Worked example — a regulated EU insurer, three months, 14 named approvers
One brief. The Oracles. One named human approver at every gate.
Below is a verbatim run through the pipeline. Every stage names a human approver and shows the typed reason they wrote before they released the next stage. No averaging, no silent drop. The case file at the bottom is the receipt.
Audit trail · one-page export
Download this worked example as a single-page PDF for your compliance officer — brief, council, ruling, sign-off, and the scaffold disclaimer in one sheet.
§ 01 · The brief as submitted
One concrete case: an EU insurer, 3,200 monthly claims, a four-line guard-rail.
What follows is a verbatim worked example — the buyer's brief, the oracles' reading, the Elder Oracle's reconciled ruling, and the five agents that turn it into a runnable Software Build. No abstraction, no fictional narrative.
§ 02 · The Oracles
The Oracles — five fixed-remit voices, tuned to opposing defaults.
Five oracles, fixed remits, opposing defaults. Each oracle is tuned to a single angle. They open objections by default, not by exception. If the oracles cannot settle the case after one round of debate, the Elder Oracle stops the run and asks you, the human.
§ 03 · The Elder Oracle's reconciled ruling
Build — with two carried-forward items, not silently dropped.
The Elder Oracle sides with Risk (a named human-only assertion step is added to the workflow, by structure) and with Growth (a typed note goes to the buyer on what the build unlocks downstream). The case advances to the Software Build.
§ 04 · The pipeline
Five named approvals, no hidden steps — operated by five specialist agents.
Each stage advance (1..5; stage 5 = Software Build) requires a human approval by name, with a typed reason attached verbatim. Five specialist agents — Discovery, Readiness, Workflow, Governance, AI Build — operate the pipeline, with Partner handing the approved build to the buyer and Impact measuring the outcome; AI Build (Agent 5) runs the Software Build stage (Stage 5). Returns are cheap; stops are free. Nothing jumps a gate.
§ 05 · Agent 5 · AI Build · working solution
The runnable output — the audit trail is the warranty.
What Stage 5 (Software Build) actually ships: a per-claim review queue with a human-in-the-loop approve / request-info / refer-to-SIU workflow, an append-only prisma audit-trail model, and an immutable per-case hash chain. Not a video. A receipt.
§ 06 · Supervisor sign-off
Read the audit trail bottom-up.
A compliance officer can read this page and trace every approval — who signed, what they wrote, when. The case file is the receipt; the receipt is the article 12 / article 14 evidence.
Want the mechanics spelled out first? Read how THE Oracles work for the five oracle remits, the three verdicts, and the Elder Oracle's tie-back-to-human rule. Or leave a one-line brief to start a run on your own case file.