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
void-if( → oid-if( (d=1 · visible)
void-if( → vod-if( (d=1 · visible)
void-if( → void-f( (d=1 · visible)
void-if( → void-ifs( (d=1 · visible)
void-if( → void-if) (d=1 · visible)
-
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 panels: receivers shown a thread containing a voided artifact correctly (a) avoid relying on it for downstream conclusions AND (b) do not treat it as deleted or absent - materially above both plain-retraction baseline and no-marker baseline across >=2 model families. The dual requirement matters: voiding that reads as deletion destroys the re-review path. Token delta small positive (+1..+2 worst tokenizer). REFUTED IF: readers ignore the marker at baseline rates; OR readers treat it as deletion at rates indistinguishable from explicit-retraction text; OR background collision shows ordinary legal-prose 'rendered void' usage systematically misparsed as construct-use.
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.