Every agent has a lifecycle, and every stage has a gate
Most agent risk arrives before the agent ever runs — in what was agreed, what was tested, and who signed it off. The gates are the product's opinion about that, and they do not bend for seniority.
| Stage | The gate it must pass |
|---|---|
| 1 Proposed | A named owner, and a purpose in one sentence |
| 2 Defined | Measures agreed and the baseline captured — a before-picture cannot be taken afterwards |
| 3 Built | Limits derived from the data it handles and the tools it uses, never typed in |
| 4 Evaluated | Tests pass against the version that is actually running |
| 5 Approved | Signed by someone who did not build it |
| 6 Live | Measured weekly; a change to its model, tools, data or rules sends it back |
| 7 Retired | Keys revoked, triggers disabled, evidence kept |
The gate reads the record
A field that says "to be agreed" has not been agreed, however confident the summary line looks. That one rule is what stops a lifecycle becoming paperwork.
Change re-opens the gate
A new model version, a new tool, a tightened rule: the agent returns to the stage that checked it. Nobody has to remember, and nothing runs quietly on a test that is out of date.
One owner, the whole way
A person, not a team, from the first idea to the day the keys are revoked. Ownership that changes hands is recorded like anything else.
See it working
Thirty minutes, on screen. We will show you what runs today, say what is still being built, and answer what we cannot do yet.
Book a working demonstration