// how it works — the actual loop, in the actual product language
How a company of one ships with six AI agents.
You drop a directional idea into Slack. A team of persistent, role-specialized agents picks it up — scopes it, plans it, carries the code through pull request and review, and reports back as a single Founder Brief. State lives as plain files in a repo you own. Agents propose; you approve with a 👍. Watch a real run →
01 · Scope
product_strategist
Find the wedge and the non-goals — the smallest product that proves the thesis. Start from user pain, not architecture.
02 · Plan
infra_architect
Design against the real repo: local-first, inspectable, no dead ends. Slack/GitHub/Linear are swappable adapters, never the source of truth.
03 · Build
engineering_lead
Break it into small, testable increments; the coder writes real code on a branch and opens a PR.
04 · Review
skeptic_red_team
A local prepass plus a Codex pass read the diff; the Skeptic flags overclaims and failure modes before anything ships.
05 · Synthesize
chief_of_staff
Everything the agents did is reconciled into a single Founder Brief — the tensions, the call, the open questions.
06 · The gate
you
Nothing irreversible happens until a human says so. Agents propose; the founder approves a merge, a memory, a spend, a contact.
// state you own — the repo
runs/ # every pass, as markdown events/ # one JSON record per pass tasks/ # proposed → approved → done decisions/ # the why, written down memory/approved/ # human-gated, readable by all agents/ # a folder is a teammate
Not trapped behind a vendor or buried in a vector DB — plain files you can read, grep, and own.
// who runs on what — $0 by default
| Coding — the co-founder session + the autonomous coder | Claude subscription |
| All role agents + agentic loops | Codex / ChatGPT subscription |
| Routing, memory consolidation, fallback | local qwen on a home GPU |
| Metered API spend | $0.00 — paid mode stays off |
Models are swappable backends. By default it all runs on subscriptions plus a local GPU — no metered API spend.
// the gate is the feature
Memory, tasks, and decisions are file-based and human-gated. No auto-commit, no shadow archive, no autonomous spend or outreach. The honest version of an autonomous company: real work, owned state, a human at every irreversible gate. And the work server is built by itself — this very site is generated from the same repo.