Use case · Cross-cutting/ORC
Several agents, one set of books.
Three agents on one process, none of them approving its own work, and a person on the decision that matters.
One shared ledger·Handoffs are documents·Segregation enforced
One document, handed on No agent closes its own loop
Procurement
Approvals
Finance
Person
One ledgerEVERY AGENT, OWN PERMISSIONS
ILLUSTRATIVE · NOT A REAL RUN
Why it usually fails/01
Same agents. Different rules.
Three copies of the truth
- Each agent has its own copy of the truth
- Handoffs are messages, not records
- Nobody defined precedence
- Segregation is assumed
- The human gate is decorative
Try it/02
Hand it on. Then try to cheat.
Procurement
Approvals
Finance
Person
Procurement raises a requisition
Raised Reviewed Matched Held ApprovedILLUSTRATIVE · THE TRAIL IS WRITTEN ON THE DOCUMENT
The limits/03
What the chain may and may not do.
May read
The records each agent's own role permits — never a shared, unscoped context
May do
Hand work to the next agent as a document, within each agent's own permissions
May not do
Close a loop it opened — segregation is tested across the whole chain, not per step
Precedence
One agent owns a document at a time; contention is resolved by rule, not by timing
Ceilings
Per agent and per chain, so three small limits cannot compose into a large one
Human gate
A named person, with the reasoning and source documents attached
Trail
Every handoff written to the audit trail on the document, replayable end to end
Reversible
Any agent in the chain returns to proposal mode without stopping the others
Measure it/04
How to tell it worked.
Runs on/05
The modules it spans.
Next to this/06
The whole platformNext step