Governed development: how our agents ship work orders through review gates
Agents write code and close work before anyone reads it. Governed development is the discipline that answers for it: scope fixed in a work order before code, separate lanes to build and to check, evidence carried with every hand-off, and a named person who approves what ships.
The short answer
Governed development is a way of running AI coding agents so that everything they build can be answered for.
Scope is fixed in a work order before any code, building and checking run as separate lanes, evidence travels with each hand-off, and a named person approves what ships. It is how Mercury's own agents work.
Governed development
Governed development is the practice of building software with AI agents under a written scope, with separate lanes to build and to check, recorded evidence at every hand-off and a named human approver, so that no agent's own verdict can release its work.
What goes wrong when coding agents ship unreviewed work?
Agents now write code, run their own tests and report the work done, often before anyone has read the change. A green test run or a confident summary gets treated as sign-off. When someone later asks what was checked, by whom and against which scope, the answer is scattered across chat history. And a claim about what the agents achieved travels with nothing underneath it to check.
Security practice already has a name for the underlying risk. The OWASP Top 10 for LLM Applications describes Excessive Agency as the vulnerability that enables damaging actions in response to unexpected, ambiguous or manipulated outputs from an LLM. A coding agent that can merge its own change holds that kind of agency over a codebase, and nobody is placed to stop a bad change before it lands.
Who is governed development for?
It is for technical founders and engineering leads who already let agents write code, and whose agents' output reaches a main branch, a release or a published page. It also answers a buyer's question about any vendor that builds with agents: when the agents built something, who checked it, and who let it through?
How does governed development differ from ungated agent coding?
| Question | Ungated agent coding | Governed development |
|---|---|---|
| Who sets the scope | The prompt, as the agent read it | A work order whose acceptance criteria are written before any code |
| Who checks the work | Often the agent that wrote it, by running its own tests | A separate lane that did not build it |
| What the reviewer reads | The agent's summary of what it did | The commands each lane ran and what they returned |
| What a pass means | The change can merge | One input to a person's decision |
| Who lets it ship | Whoever presses merge | A named person who read the work, the evidence and the verdicts |
| What may be claimed afterwards | Whatever the summary says | The proof step sets the test: a definition, a baseline, a period, a counting method and a source |
How it works, step by step
Scope is fixed before code
Separate lanes build and check
Evidence travels with the hand-off
A checking verdict feeds the decision
The human gate: a named person approves what ships
A proof step for claims
Where does governed development stop?
It does not make code correct
A reviewer can miss a defect. The gate records who approved the change, so a miss traces back to a decision and a name.
It does not hand out autonomy. Whether an agent may ever act without a gate is a separate decision, made on evidence. Shadow mode covers how that is earned.
Some work stays with people
What never goes to an agent is its own question, answered on the when not to automate page.
It carries no result of its own
What the practice achieved is a measurement, and the proof step says what that measurement needs.
Where this fits
Governed development is a concept page under the AAOS platform, which describes what a work order holds. How It Works covers where the holds sit in an engagement. Two other concept pages explain how work arrives in the first place: the work order you didn't create, and when the system notices your busywork. Every page in the series is listed in the use case library. For business processes rather than code, the readiness checklist tests whether a workflow is ready to hand to an agent at all.
Related reading
- Approval gates: how to keep humans in the loop without slowing down: what a gate is and where it goes.
- Shadow mode: how agents earn autonomy: when an agent may earn a step of autonomy.
- Plans vs routines: the shape a build is governed as.
