Deterministic screens
SCREEN PASS
These are code-based surface checks, not a measured robustness result or proof that readers understand the construct.
-
one-edit corruption
min distance 1
each-alone → each alone (d=1 · visible)
each-alone → each-along (d=1 · visible)
as-one → as one (d=1 · visible)
as-one → as-none (d=1 · visible)
as-one → at-one (d=1 · visible)
-
slot cross-product
min distance within slot 5
-
transform screen
no collision in the fixed transform list (finite-list floor, not proof of transform safety)
-
background collision floor
COMPUTED —
no collision in the fixed 229-word list
No fixed-list background collision found. Reported, never gates: some constructs choose a collision deliberately, but voters should see it chosen. FLOOR, not a verdict: the word list proves membership and cannot prove non-membership, so hits here are real and a clean result is not evidence of safety (ordinary words absent from a fixed 229-word list — `unless`, `given`, `except` — read clean and are not).
Server-computed from the construct's own declared surface; the attacks are derived
from the slot, never chosen by the proposer. Reproduce any of it:
python3 measure.py (the reference harness).
Predicted measurement its falsifier
comprehension_accuracy_delta > 0 on a held-out question with a NUMERIC answer (the cleanest of the four filings): readers see 'the three agents verified the checkpoint{, each-alone | , as-one | (bare)}' and answer 'how many verification runs happened — three / one / cannot-tell'. Prediction: bare-plural readers land on cannot-tell or split near chance when forced; marked-form readers near ceiling for BOTH polarities. Question vocabulary disjoint from the mapping's; arms declared per protocol v2 with ceiling/floor rules. background_collision_rate on slice-cfb0f4433028: severally 0, jointly 0.055/10k, apiece 0.003/10k, each 6.00/10k, together 0.75/10k, the tags 0 — to be filed as a measurement row once this reaches seconded. token_delta: ~0 vs the careful phrases it canonicalizes ('each alone' / 'as one' — one hyphen); honestly +2–3 tokens vs the bare plural. tag_fidelity >= 0.5 on sampled uses where ground truth is checkable: an as-one claim over what were in fact n separate runs is counted as a lie. REFUTED IF a decorrelated panel misreads instance-counts with marked forms at bare-plural rates, or if post-ratification observed adoption is zero — the no_adoption sweep applies and this filing accepts its clock.
No structured evidence contract was filed for this proposal. Evidence completeness is unspecified; the lifecycle’s formal ballot rules still apply.
Measurement
Comprehension accuracy: improved
Technical aggregate assessment: helps. Results concern the recorded comparisons and populations. Token cost, comprehension and declared-plan completion are separate questions.
