Each essential taken apart into the pieces an architect builds, the second line sets limits on, and an auditor examines. A slide for each essential, two for knowledge, two for the record, and two for the loop, and each ends with what the market sells for it.
Part one lists the parts of each essential and their owners, and part two follows one decision through the essentials. This part opens them: each slide takes one essential apart into the pieces an architect builds, the second line sets limits on, and an auditor examines, and the last slide says which pieces a firm can buy and which three joins it has to build. It assumes part one; part two is useful and optional.
About 20 minutes. Every slide builds in steps: → moves through them before it moves on. Click a line on the left to go straight to that slide.
M opens the contents, F finds a word, and T switches between light and dark.
Short of time? Choose by role: risk and compliance, slides 4 and 5; architects, 7, 8, 9, and 12; audit and the examiner, 9; model risk, 3 and 11.
Then part four turns the map to your firm.
What acts is a model inside a harness, behind guardrails, with an identity, reaching the firm’s systems through a gateway. The firm approves all of it together, as one release.
In a controlled study on software-engineering tasks, a 100-task subset of SWE-bench Verified with three near-tied models, the harness explained 7.8 times more of the variance in results than the model, a ratio its authors call not universal (Zhang et al., 2026). So the firm approves a release, not a model: a new model, prompt, or tool is a new release, validated again.
An agent relies on more than documents. Each kind has its own owner, its own versions, and a date from which it applies.
The version in force on the date of the loss, the payment, or the decision, not the latest one, and not the most similar.
The most similar passage, from any version. Usually right, wrong exactly when a version has just changed.
Each source owner keeps the record of what is in force and from when. The check, w4, asks that record at the moment of the act.
A document is a container. What can be checked, dated, and owned is the single assertion inside it: a claim, in the knowledge-layer sense. Each claim is traced to the clause it comes from, and what the firm writes for the case becomes a view on the table.
Today an agent’s authority is scattered across four places. Each answers part of the question; none answers all of it.
What was this agent permitted to do at 10:02 on 17 September, who owns that answer, and which version was in force? Only an object with an owner and a version can answer, as at any minute.
The check sits between the agent’s proposal and the system that executes it. It reads the agent, its knowledge, and its mandate, and there is no other route to the system.
Fourteen fields, written once for every act, in this order. The right-hand column is claim 4471 of the motor case; each dossier fills the same fields for its own case.
Two of the fields are version keys, the mandate and the release, and they let the decision be rebuilt as at that second. The other twelve say what it rested on, what it did, and what came back. So the examiner, the auditor, and the knowledge function read one line where today they read three systems.
The loop reads every record, and what it finds changes the parts before it. That is what makes the control plane a living system.
The set’s first rule: autonomy may not rise above evidence. Each level of autonomy needs a level of evidence, and the two directions follow different rules.
All three joins meet at the mandate, and they are what lets the control plane say no before the act. That is where the firm’s own work sits, on whatever stack it already runs. Next: one decision, through all six.