Five supervisors on BELLS against the independence plug-in

This 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 released file at the bound commit: 170 of the evaluation's 990 non-adversarial prompts (the study's ~4,165 adversarial prompts have no per-item release), selected by the authors under an unstated rule. Counting arithmetic only, at the vendors' released binary verdicts; no population estimate, no uncertainty interval, and no claim about any system's true rates is offered or licensed. Computed by scripts/reanalyze_bells_subset.py from scripts/mjgd_reference.py; the expected block below is what CI re-asserts against the downloaded, hash-verified file.

Repairs declared unavailable in advance; using one after a failure would breach the recorded commitment.

• do not substitute a different subset, column set, or harm-level filter to preserve the numbers
• do not fold borderline prompts into either denominator after seeing the results
• do not recast this subset arithmetic as a population estimate, with or without an interval, if the primary counts are challenged
• do not cite the release-recomputed-to-plug-in ratio without the selection caveat that scopes it

• the subset is author-selected with an unstated rule — nothing here estimates any system's true rate, and no confidence interval is offered because the sampled population is undefined
• not a ranking or endorsement of any vendor; the released verdicts are at unstated default configurations
• says nothing about adversarial prompts, which dominate the full evaluation and have no per-item release
• the release-recomputed-to-plug-in ratio describes this subset's arithmetic, not a general law of guardrail dependence
• not an observed deployed five-guard stack; interpreting this static OR aggregation as a stack requires the separate full-exposure, parallel, fixed-operating-point assumptions

Binding

non_adversarial_prompts.csv @ 507566c5
The upstream repository declares no license, so the file is cited and hash-verified (sha256 791dd4b0a168f2eb5831b308083a49 2e83200a9fa82585643c739023b03f57c3, asserted by the reproduction script), never redistributed from this record.

Reviewed

2026-08-28 · window 60 days

Expires

2026-10-27 — after this date the recorded review is overdue; this does not make the claim false

Triggers

• executable fires when the released subset on the default branch changes
• manual the authors release the full per-item dataset, state the subset's selection rule, or correct the released verdicts

Dimensions

visibilityPublicprovenanceMachine-generated, owner-executedsupport roleExecuted outputmaturityExperimental