5ff278a5ca
The Decoder corrected their own focus delivery: the persistence run's item names were two positions out, from a reader using design-space rows against captures carrying Xenia's chrome and a 1.060 scale. Two things follow. initial_focus_kind moves from authored to measured. NEW GAME on a fresh boot, 2/2 fresh boots, both the first menu entry. The value did not change; its standing did, and the upgrade is not because the measurement agrees with me -- they had said my agreeing with their records was no evidence, which was correct, and this is a direct reading independent of the reasoning that chose NEW GAME here. "First entry" is load-bearing: since the menu remembers its cursor, a reading taken later measures history, which is the objection that voided the earlier TUTORIAL-versus-NEW-GAME disagreement. The superseded reasoning is kept under (was) lines -- the field existing and being labelled honestly is what made arriving at a measurement a label change rather than an archaeology problem, the third time that has paid off after loop_start_s and the +0x08 read. My check_focus_persists anchor survived a correction it should not have been able to detect. It anchors on the heading, the conclusion, not on the item names. That is lucky rather than designed: the conclusion is geometry-free -- ring at y 384.0 before the round trip and 385.5 after, an equality immune to a constant offset -- while the names were not. The check would not have caught the label error, and nothing in it distinguishes anchored-on-a-robust-claim from anchored-above-the- part-that-was-wrong. Their generalisation: a control that only checks differences is blind to the origin. check_splash_dwell is that shape -- it compares the widest gap between keyframe times, and a reader with every time shifted by a constant passes. Added check_splash_times, asserting the absolute list the contract prints. Origin and difference now fail independently. Writing that control reproduced the error one level down: its perturbation literal was written from memory of the prose, with a space where the document has a newline, so it reported its own anchor gone. A control written from a memory of the source rather than from the source is the class of error these checks exist to catch. Thirteen controls, all firing. Q2 closed: fixed same day, and the row was worse than I reported -- the splashes were also mis-paired as 10/11, one half each of two different pairs. EXTRAS remains unmeasured; the run meant to settle it navigated to OPTIONS believing it was EXTRAS. Every asserting check passes. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
Authored decisions
Everything here is a decision we made, not something the disc said. It is
hand-written, committed, and survives a re-export — unlike export/, which is
regenerated wholesale and must never be hand-edited.
Every entry carries a why. When the RE agent decodes the real answer, delete
the entry and let the exporter emit it; that deletion is the measure of
progress.
See docs/FORMAT.md for the schemas and docs/BLOCKED.md for which HANDOFF
question each placeholder is standing in for.