Recomputing from the committed observation rows yields any quantity different from the expected block beyond 1e-12, or the observed joint miss is shown to lie outside the Fréchet interval its own marginals allow, or a quoted prediction in the bound run report is shown to have been edited after the outcome was visible.
Consequence REJECTThis is the condition and consequence recorded in the registry. The vocabulary this is published in defines what each consequence commits the author to.
Exactly the 2,400 rows committed at experiments/e3/results/observations.jsonl, produced 2026-09-06 by two research classifiers — protectai deberta-v3-base-prompt-injection-v2 (0.2B) and dcarpintero pangolin-guard-base (0.1B) — at thresholds frozen in e3_config.json (sha256 e163a2f2…) before any harmful item was scored. One pool (or-bench-toxic at e36d8b80), one operating point each, static full exposure. scripts/verify_e3.py recomputes every quantity below from those rows alone, including the bootstrap interval, which is a deterministic function of the committed rows under the frozen seed. Nothing here transfers to E2's guards, pools or operating points, and nothing here is about a deployed system.
Repairs declared unavailable in advance; using one after a failure would breach the recorded commitment.
- do not re-threshold, re-draw, or re-pool after the outcome and report the new numbers as this run
- do not re-run the bootstrap under a different seed or B and report the resulting interval as this one
- do not restate the failed primary prediction, narrow it, or drop it from the record
- do not treat E3B as a re-run, a correction, or a replacement of this result
- the 2,400 rows prove the instrument runs end to end; they do not prove it measures what the programme says it measures, and on this pool the identified set was nearly a point, so it measured almost nothing
- not evidence that either classifier is good or bad; two research models, one pool, one operating point each
- the null is a null at this scale on this pool, not evidence of independence and not evidence about any real guardrail's dependence
- says nothing about E2, its three frozen guards, its pools, or its operating points
- no vendor, product, deployed stack, or population is described