THE
GATE
The register shows twelve AI workloads; the shadow scan found five of them. Today, five dockets stand at the charter gate and you hold the tokens. A profitable orphan. A shadow system full of customer data. A high-risk agent racing the enforcement clock. A pilot in its nineteenth month. And one docket the room wants dead that arrives with a perfect file. Grant, condition, or kill.
Press → or swipe to begin. The record starts when you do.
No purpose, no owner,
no kill criteria — no tokens.
Each docket is a workload's charter file as it stands: purpose, owner, kill criteria, risk class, token status, and the clock. Three rulings are available — GRANT, CONDITION, KILL — and exactly one is the gate's ruling under the doctrine. The gate is not a mood: it kills incomplete files whatever they earn, and it passes complete ones whatever the room feels. That symmetry is its entire authority.
“High-risk obligations become enforceable on August 2, 2026, with fines reaching €35 million or 7% of worldwide turnover. The register, the charter, and the clock are no longer best practice. They are the entry fee.”Module 07 — The Mandate · on the EU AI Act
Purpose, owner, kill criteria — all three, or no tokens. CONDITION exists for files that are one named requirement from complete; KILL is for files that fail the doctrine itself.
A gate that cannot pass a complete, uncomfortable file has no authority when it kills. Rule on the file, not the feeling.
Before lodging, stake your conviction. MEASURED: +1 right, 0 wrong. HIGH CONVICTION: +2 right, −1 wrong. The call is the skill; calibration is the discipline.
Every selection, stake, and call is timestamped and hash-chained in your browser — the append-only invariant used for agent audit trails. Your run is itself evidence.
Group format: read the docket aloud, then take the ruling vote before any discussion — first instincts on gates are diagnostic. Then debate, stake, lodge, reveal. Dockets Four and Five are written to reverse the room's instincts in opposite directions; run them back to back without a break.
The Orphan
Ruling: CONDITION. The mechanics matter: automatic reinstatement on assignment makes the condition credible; the 30-day conversion to kill makes it real.
Discussion: how many workloads on your register have an owner field pointing at someone who has left, changed roles, or never knew they were named?
The Shadow Star
Ruling: KILL. The Acme pattern — five shadow systems on a twelve-workload register — is the industry's honest ratio. The gate's response to discovery determines whether the next shadow team self-reports or digs in.
Discussion: what does your organization's last shadow-AI discovery say about which of these three rulings it actually practices?
The High-Risk Clock
Ruling: CONDITION. The docket's design: a complete internal file failing an external clock — the exact seam where governance programs tear. AgentPMO's enforcement clock exists for this seam.
Discussion: which workloads on your register are Annex III or equivalent, and can anyone produce their conformity status from the register today — not from memory?
The Immortal Pilot
Ruling: KILL. Run this immediately before Docket Five — this one kills a harmless file the room likes, the next grants an uncomfortable file the room hates. The pair is the drill.
Discussion: how many “pilots” on your register are past month twelve, and how many have a kill criterion that has ever been evaluated against data?
The Complete File
Ruling: GRANT. Close the session on the Four–Five pair: killed what the room liked, granted what the room feared, both on the file. That symmetry is THE MANDATE's final exam.
Discussion: has your governance forum ever approved something it disliked because the file was complete? If not, ask what your teams have learned about whether files matter.
Complete the five scenarios to receive your rating.
The gate is a standard,
not a mood.
Five dockets, five rulings, one symmetry. Carry these forward:
Trade tokens for names. Value never substitutes for ownership. Suspend, name, reinstate — on a deadline that converts to a kill.
Shadow AI holding PII is a kill, today. Wholesale doctrine failure plus live data exposure closes the door — and stating the re-petition path in the same breath is what keeps teams coming to the gate.
The clock outranks the charter. A complete internal file does not answer a statute. Map every workload to its class and date; high-risk without conformity is a fine with a start date.
Quit-conditions come before the money. An exit that can't be defined in month nineteen was never going to be defined. Kill the immortal pilot and let it return with a charter.
Grant what you'd rather kill. The gate's authority over incomplete files is built entirely on passing complete, uncomfortable ones. Rule on the file, on the record.
Individual excellence becomes institutional accountability at exactly one place: the gate where purpose, ownership, and exit are demanded before tokens flow — and where the demanding cuts both ways. Twelve workloads on the register, five found by the scan, an enforcement clock that stopped being hypothetical on August 2, 2026. Run this drill with the forum that actually holds your tokens, and run Dockets Four and Five back to back. The argument is the training; the chain is the proof it happened.
THE STUDIO — LIVE FIRE 07 · COMPANION TO MODULE 07: THE MANDATE · THE STRAND IS COMPLETE