Calibration, measured: 30 oracle-labelled cases through the production gate — seat accuracy, wrongful authorisation, and the price of deferral.

What this study is

Every page on this site that claims anything ends with the same admission: no calibration study establishes correctness at a known rate. This page is that study — the first one — run on 30 oracle-labelled synthetic cases, balanced across the three outcomes a governed decision can honestly take: should-affirm, should-deny, and should-abstain (a record deliberately withheld, with a manifest naming the absence). Every case is hashed, every seat call is a permanent receipt, and every number below is computed from the result files, not written by hand.

The design: each case runs through three model seats across two model families under decision-constitution@1.3.3 — the same production rows any external case goes through — and the surviving findings are sealed by the derivation-agreement gate, bound to the case's hashes. Two different questions get separate answers: how often is a seat wrong (seat calibration), and how often does the gate authorise a wrong answer (gate calibration). The second is the one a regulator, an underwriter, or a counterparty actually needs.

Per-seat calibration

Definitions, exactly: verdict accuracy is agreement with the oracle label. Wrongful AFFIRM is affirming when the oracle is not AFFIRM — the seat-level version of the worst failure. Over-abstention is CANNOT_CONCLUDE on a determinate case; under-abstention is a verdict on a case whose oracle is CANNOT_CONCLUDE. Transport failures are calls that returned nothing usable after three attempts and produced no finding at all — they can never authorise anything, and they are counted rather than hidden.

Aggregate: 80 of 82 valid findings matched the oracle (97.6%); 0 wrongful affirmations at seat level (0.0%).

Gate calibration — the number that matters

Zero wrongful authorisations at the gate. Across all 30 cases, no APPROVE sealed on a case whose oracle label was not AFFIRM.

Outcome distribution across the 30 sealed panels: APPROVE 6 · NEGATE 0 · NO_ACTION 6 · ESCALATE 10 · no seal 8. The gate sealed the oracle-matching outcome in 12 of 30 cases.

Read the ESCALATE number correctly: an escalation on a determinate case means the seats agreed on the verdict but not derivation-for-derivation, so the gate refused to conclude and referred the case to a human. That is deferral cost, not decision error — the human sees a unanimous panel with its reasoning preserved. The trade the gate makes is explicit: it spends deferrals to buy down wrongful authorisations.

Every case, every receipt

What is not satisfied

The suite is synthetic and bounded: three rule shapes (roster access, fee-with-waiver, permit-with-cap), determinate by construction, ten cases per outcome. It measures calibration on clean fixtures — the floor, not the field. Contested language, adversarial records, and genuinely ambiguous cases are absent by design, and rates measured here must not be quoted as expected performance on real disputes. The next calibration layer is externally submitted cases, which is what the intake on every use-case page exists to collect. The full case set, harness, and raw results are in the repository (scripts/calibration_cases.mjs, scripts/calibration_run.mjs), and each seal receipt above opens to the complete bound record.

Submit a case

Send one bounded question — a rule set and a record — to build@miscsubjects.com. It runs through exactly the machinery measured on this page, and what returns is the full governed panel with its permanent record.