The records
Plans, decisions and requirements, each one versioned and pinned to the code it describes. A product's Standard says how its work is done, and every plan is held to it.
CASE STUDY
onMain
The tool we run every engagement in. It started as our own client portal, it built itself, and it's now a product other teams and agencies use.
The problem
Software projects run on documents: a spec, a plan, a deck, a wiki page. They're written once and drift from what ships, and by the time a decision matters again, nobody can find why it was made.
Coding agents made it worse and better at once. An agent can build fast, but only from context it can read, and documents in someone's drive aren't it. Meanwhile the client paying for the work sees a status email and has to take the rest on trust.
Records, not documents
The idea everything else hangs off: the plan and its reasons are data, versioned on the same branch as the code.
The agent's way in
A coding agent reads and writes those records through an MCP: it claims a card, reads the plan and the decisions behind it, and records the pull request and the release when it's done.
The client's view
A portal over the same records, so the client sees the plan, the progress and the status reports, and the inquiry that started it all is the first entry in the trail.
Built with itself
Every plan, decision and card behind onMain lives in onMain. So does this website's.
266
plans written and landed
110
decisions on record
325
cards finished
8
products it builds, client work included
Counted from onMain on 8 October 2026. Every engagement runs in it — see how we work →
Want your project built this way?
Every engagement runs in onMain, with the plan and every decision written down where you can read it.