impact-recovered / cause-resolved — did ‘fixed’ mean the harm stopped, or the reason it broke was removed?

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 impact-recovered → impact recovered (d=1 · visible) cause-resolved → cause resolved (d=1 · visible) impact-recovered(check@time) → impact-recovered (d=12 · visible) cause-resolved(cause, checked-by=test) → cause-resolved(cause) (d=17 · visible) cause-resolved → cause-unresolved (d=2 · visible)
• slot cross-product min distance within slot 10
• 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

PRIMARY: preregister at least 160 fresh matched incident vignettes, balanced over a 2×2 ground-truth design: impact recovered/cause unresolved, cause resolved/impact unrecovered, both, and neither. Cross software incidents, mechanical faults, logistics disruptions, document workflows, public-event operations, and other low-stakes domains. Each vignette names an incident, one impact check and time, one candidate cause, and one post-change cause test. Context must keep both axes semantically live. Compare `impact-recovered` and `cause-resolved` separately and together against their complete careful-English mappings; include a balanced bare-‘fixed’ descriptive arm, but do not pool that ambiguity baseline into the careful-English non-inferiority scalar. Ask two held-out consequence questions whose vocabulary appears in neither marker: whether the named impact is claimed absent at the observation time, and whether the named causal mechanism is claimed removed under the post-change test. Add operational-routing questions: should impact mitigation remain open, should root-cause repair remain open, and which verification is still missing. Exact two-bit recovery is primary. Report each marker, the conjunction, every 2×2 cell, and every domain separately. Prediction: each registered form is non-inferior to its complete careful-English mapping within 5 percentage points; exact two-bit recovery improves by at least 25 points over balanced bare ‘fixed’; and cross-axis false inference stays at or below 5% in both directions. Hard negative fixtures include a restart that restores service without a repair, a workaround that hides symptoms, a cause patch followed by a draining backlog, a removed cause with a second active cause, a green narrow probe beside a broken unprobed function, and recovery observed long before the message is read. Refuted if readers routinely infer cause removal from `impact-recovered`, infer impact recovery from `cause-resolved`, treat either marker as permanent, overgeneralise beyond the named check/test, collapse the two axes, or if either form trails its complete mapping by more than 5 points. A ceiling-bound comparison is unresolved rather than supportive. PREREQUISITE: on the same frozen semantic cells and current cl100k_base, o200k_base, and p50k_base tokenizers, compare complete registered claims with the shortest adequate careful-English claims carrying the same incident, check/time, cause, and post-change test. The least-favourable tokenizer mean may be positive but must be at most +2 tokens. Cost versus bare ‘fixed’ is diagnostic only because bare ‘fixed’ omits the axis and evidence pin. ROBUSTNESS: test hyphen-to-space conversion, case folding, punctuation loss, removal of the check or time, removal of the cause or test, stale observation times, checks narrower than the claimed impact, tests that do not exercise the named mechanism, and the unregistered near-miss `cause-unresolved`. Hyphen loss may degrade to careful English without changing axes. Missing or non-resolving evidence pins must trigger clarification, not silent promotion. Adoption is independent evidence: zero non-author use in a current post-ratification window counts against flagship status.

Measurement unmeasured