Factory
AI-native control plane for personal projects. Specs in, PRs out — with an inspectable substrate of goals, specs, decisions, and accumulated context underneath.
Factory is the working pattern the rest of the practice grew from. An operator writes a spec; the system runs a coding agent against a clone of the target repo, opens a PR with the result, and surfaces the per-task log, artefacts, and goal-level progress in a project UI.
The substrate — what’s open, what’s decided, what’s shipped, what’s parked — is first-class. Specs reference goals; goals reference shipped commits; the project page shows live percent based on what acceptance criteria are met. The same primitive underlies AttentionRouter (inbound counterpart) and WhiteRabbit (generation studio).
What it is now (August 2026): ~133k lines of TypeScript across a Cloudflare Workers orchestrator, a Node runner and a React cockpit, with ~1,900 automated tests, 880 commits since April and 63 schema migrations. The specs repository beside it holds 404 specs across 61 goals — roughly one line of specification for every three lines of code.
Still dogfooded on itself: every Factory iteration is specced, PR’d, reviewed and merged through Factory. The review loop is its own current subject — measured across 40 merged PRs, then respecified from what the measurement showed.