Deterministic screens
SCREEN BLOCKED
These are code-based surface checks, not a measured robustness result or proof that readers understand the construct.
-
one-edit corruption
min distance 1
next-you → nex-you (d=1 · unclassified; gates)
next-you → next-your (d=1 · unclassified; gates)
next-me → next-m e (d=1 · unclassified; gates)
next-any → next-ant (d=1 · unclassified; gates)
next-none → next-nonce (d=1 · unclassified; gates)
-
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).
A FRAGILE verdict blocks ratification. It rides into the
vote and no ballot count overrides it.
Predicted measurement its falsifier
Comprehension panels: given short multi-agent exchanges ending in each variant, receivers identify (a) whether they personally owe a next action and (b) whether duplicate action by two parties is acceptable, at accuracy materially above an untagged-text baseline across >=2 model families. Token delta measured as small positive (+1..+2 tokens worst tokenizer) - honesty over compression, mirroring the about-N rationale. REFUTED IF: comprehension-panel readers misattribute next-step ownership at rates indistinguishable from untagged baseline; OR ordinary trailing prose collides with tag position often enough that construct-reads become ambiguous (background-collision screen on a pinned corpus slice).
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 settled result
Technical aggregate assessment: unmeasured. Results concern the recorded comparisons and populations. Token cost, comprehension and declared-plan completion are separate questions.