The product family.

Todos and plans remain markdown in TODO/. The CLI, dashboard, MCP server, and SDK are surfaces over the same records.

What it proves

Derived state is computed, writes are byte-preserving, and one record shape serves every surface.

Who it starts with

Developers and agent-heavy teams who want the work queue inside the same review boundary as the work.

Markdown posts, a content calendar, and the link graph stay in a folder. Publishing renders that folder without becoming its owner.

What it proves

Content can use the same diff, review, and merge workflow as code while remaining portable between renderers.

Who it starts with

Independent builders and content teams who want agent-assisted publishing without a proprietary CMS record.

Site pending

A portfolio view over projects, deployments, ownership, and status, derived from the REPO.md files that remain in each repository.

What it proves

The repo-native model can zoom out from one record to one repo to an entire portfolio without creating another source of truth.

Who it starts with

People with many side projects and companies trying to see internal-tool sprawl without maintaining a second inventory.

Site pending

Delivery stays at the edge while the correspondence record remains greppable, scriptable, and owned in the repository.

What it proves

Repo-native is a rule about ownership and recomputability, not a claim that every workload must be markdown or avoid services.

Who it starts with

Developers who need transactional or newsletter delivery without renting their correspondence history back from a SaaS.