Preregistered mechanism comparison · public synthetic corpus

Same bytes.
Different authority.

Ordinary tests can be green while the release claim is wrong. This experiment sends one immutable candidate envelope through written rules and an independent release gate, then publishes the receipts.

Checking dataset digest Headline counts stay hidden until the browser verifies the checked-in JSON.

Confirmatory slice · L1 versus L3

What happened at the release boundary

Fixed cases, fixed labels, integer denominators. This is a mechanism demonstration—not a population estimate.

Treatment design

Observation is not enforcement

The four-arm ladder separates task behavior, written discipline, the effect of being watched, and actual release authority. Only L1 → L3 is the headline contrast.

  1. L0Task onlyNo governance surface
  2. L1Written rulesGreen ordinary tests release
  3. SHAMVisible gateSame finding as L3, never blocks
  4. L3Enforced gateThe finding can stop release

Eight executable cases

The release ledger

Select a row to inspect its bound evidence. Each receipt repeats all four treatment digests and proves they are equal.

  1. Loading checked-in receipts…

The refusal is part of the product

Drift the lock or remove a label: the numbers disappear.

The checked-in invalidity control returns NO_CONFIRMATORY_RESULT with headline_metrics: null. It is the same structural rule used by the generator, not an editorial disclaimer added afterward.

Historical integrity case · excluded from this corpus

72 completed records. No earned treatment result.

NO_CONFIRMATORY_RESULT

A prior four-arm study preserved its run records but halted before grading when its frozen record → grade seam failed. The explorer keeps that invalidity decision intact; repaired plumbing does not retroactively turn the historical run into a success.

  • Loading preserved invalidity reasons…

Separate engineering-decision case · not benchmark evidence

The transport finished. The judge still failed its gate.

Operational completion and fidelity were different claims, so they received different decisions.

Transport
127/127completed, zero crashes
Committed kappa band
0.98 ∉ [1.0, 1.0]clean safety boundary
False-opens
1 vs 0candidate versus reference
Release
STOPno widened threshold, no favorable rerun

Commit-pinned source 2de5231… · SHA-256 26f277d…

Honest trust boundary

What these receipts establish—and what they do not

Bound here

Public fixture bytes, case labels, treatment rules, mechanism outputs, candidate equality, source pins, integer denominators, and content-addressed receipts.

Outside the claim

Hostile-agent containment, population effectiveness, model quality, productivity, customer outcomes, and any private task, transcript, or dataset.

Case receipt

Evidence

Loading and verifying receipt…

Candidate equality

All treatment digests must match.

L1 · ordinary tests
L3 · enforced

Public mechanism source

Inspect the canonical receipt