The product family.

Agents and people plan, execute, and hand work off against Markdown records in TODO/. The CLI, dashboard, MCP server, and SDK are surfaces over the same files.

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.

Agents draft and revise Markdown posts; humans review the diff; publishing renders the folder without becoming the owner of the content record.

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 boundaries, and relationships, derived from the REPO.md files that remain with their repositories.

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

Agents can search, draft, and reason over a repository-owned mail record while a specialized service handles delivery at the edge.

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.