The production line
Nine stages, in two halves.
In the first four, people think it through with an agent: the person leads, the agent researches, drafts and pushes back. From work orders on, agents do the work and people hold the gates. The last stage runs backwards and reopens the conversation.
Foundry SenseIdeate and design, stages 01–04. Your people lead; the agent researches, drafts and pushes back.
Foundry DeliverDevelop, deploy, support and enhance, stages 05–09. Agents do the work; your people hold the gates.
01 · IntakeEverything your team hears, in one place
Customer calls, support threads, sales notes, meeting notes, the idea someone had on the walk in — each tagged to the Genome process it touches. Anyone can add. Nobody decides anything here.
02 · Triage gateEvery input gets a call and an owner
The agent proposes: a bug, a change to something you already promised, a new promise, or noise. Your product owner pushes back until the call is right and has a name on it.
03 · Requirements gateWhat the product must do
Each requirement cites the conversation it came from, the Genome node it serves and the KPI it should move. Where two inputs contradict each other, the draft says so instead of quietly picking one.
04 · Blueprint gateHow it will be built
The technical plan, drafted from the requirements. Each part says which requirement it serves and which systems it touches. A working session with your technical lead, not a sign-off.
05 · Work ordersAgent-sized pieces of the plan
The blueprint is cut into work orders an agent can finish in one sitting, each carrying its part of the plan and the requirement behind it. Your lead reorders, merges or drops them.
06 · BuildAgents, in your repository
An agent takes a work order and opens a pull request. If what it built changes the plan, it updates the blueprint in the same pull request. Your engineers review it as they would any other.
07 · VerifyEvidence, not a green check
The Eval Harness runs the checks each requirement names. The result attaches to the work order: what ran, against which version of the requirement, and what it found.
08 · Review and accept gateThe human gate
Every proposal, from a triage call to a code change, waits for a person. The Foundry shows what will change and why. It never applies anything on its own.
09 · BackpropagationThe loop that keeps the rest honest
Change a requirement and every plan and work order built on it is flagged. Ship code that departs from the plan and the plan's owner sees it. The Genome is updated so your documents describe what you actually have.
L1Suggests
The Foundry proposes; a person does the work. Used on anything new until the evidence exists.
L2Acts with approval
The Foundry prepares the change in full; a named person presses go. Most work sits here.
L3Acts within limits
Runs unattended inside agreed thresholds — value, volume, blast radius — and escalates outside them.
L4Runs unattended
Only for low-risk, well-evidenced loops with a proven rollback. Reviewed, not assumed.
One rule holds the whole line together: nothing moves to the next stage without naming what it came from — the conversation, the requirement, the Genome node, the number it should move.