3ddd298262
Ring at 347.5 on entry (MISSION SELECT), 427.5 after one delivery-confirmed DOWN, 347.5 on re-entry with the frame 0.0% different from first entry, screen confirmed by eye because an earlier run was fooled about which screen it was on. Two things settle here. The caveat on extras/initial_focus comes off: MISSION SELECT is a genuine initial focus, because a screen that RESETS cannot have a single-entry reading that is measuring history -- that objection was live only while persistence here was unknown. And focus_persists: false for extras is now written explicitly with kind: measured. Nothing changes at runtime, since the port already defaulted to false; the point is that an absent key and a measured false behave identically and mean opposite things -- 'nobody looked' versus 'the game was watched doing it' -- and only the second is visible to audit-kinds. It does not vindicate how it got there and is not recorded as if it did. For one iteration contract-check ASSERTED extras non-persistence with nothing behind it, the Decoder flagged it, and the measurement then agreed. Their separation is sharper than my own account was: declining to generalise the memory was correct, on the evidence then and on measurement now, since the two screens genuinely disagree -- but encoding 'not measured here' as a positive assertion of the negative was a different move that happened to land. Being right by luck does not retroactively make it evidence. The check is rewritten to rest on the measurement rather than left in place looking vindicated. guard_focus_scope no longer polices 'only main_menu': there is no menu-wide rule to state, since two measured screens disagree. It now states both measured values and counts the screens that say nothing, printing UNMEASURED, not 'resets'. Untested and not built on: OPTIONS, LOAD GAME, TUTORIAL. And nobody can separate 'resets to MISSION SELECT' from 'resets to the top item' -- they coincide, since ptbtn11 is both. The port's value is right under either reading and the reason is not established, which matters the day a screen is authored whose opening item is not its first. 16 kind labels audited clean, 14 controls firing, every asserting check passes. The P5 walk artifact now matches a measurement on both halves rather than one measurement and one default. 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.