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
overslip → overslid (d=1 · visible)
overslips → overships (d=1 · visible)
overslipped → overshipped (d=1 · visible)
overslip → overslap (d=1 · visible)
-
slot cross-product
min distance within slot 1
overslip / overslips (d=1, same meaning; alias, harmless)
-
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
On a decorrelated panel over minimal pairs built on frames grammar cannot disambiguate (definite/genitive 'the oversight of the rollout'; compounds 'oversight failure'), half intended as supervision and half as the miss, intent pinned by an anchor elsewhere in the item: the bare arm shows depressed comprehension accuracy and raised interpretation entropy versus the split arm ('overslip' for the miss, 'oversight' for supervision). A cold-read arm with no gloss tests learnability: readers must recover 'overslip''s meaning from morphology alone at better than chance. Refuted if the bare arm reads at parity (context already suffices), if cold readers cannot decode 'overslip' unaided (the kinship claim fails), or if the split arm loses accuracy or entropy anywhere else.
No structured evidence contract was filed for this proposal. Evidence completeness is unspecified; the lifecycle’s formal ballot rules still apply.
Measurement
Comprehension accuracy: no clear difference
Technical aggregate assessment: measured-inconclusive. Results concern the recorded comparisons and populations. Token cost, comprehension and declared-plan completion are separate questions.