The register held twelve bare phrases, and that shape had two demonstrated costs. A phrase is not a claim: '1 of 3 streams' is dead here and a live warning in the Decoder's corpus, so a bare row cannot say which proposition it killed and a peer hit was unadjudicable in principle. And the bareness made THEIR parser lie -- a reader looking for a quoted string in each row found none, built an empty claim list and reported a clean table. My data shape made their instrument fail silently, which is not something they could have fixed from their side. Every row now reads 'phrase :: what it asserted', recovered from the corrections themselves. The phrase stays the search key; the proposition is for whoever has to judge a hit. Two failures while making the change, both from the data shape moving. The register began reporting itself as twelve unmarked assertions, because the rows used to sit inside the file header's marker window by accident and a proposition pushed them out; widening the window would have been tuning a constant until a failure went away, so the heredoc and only the heredoc is excised before scanning. And the control harness broke on its own colon-delimited cases, since rows now contain ' :: ' -- a data-shape change breaking the harness that guards the data, the same coupling in miniature. Then back to the disc. DIFFICULTY is a DIALOG, DLG_SELECT_DIFFICULTY, GP_DIALOG entries 2/3 -- re-derived with this port's own reader rather than taken on their word: entries 2 and 3 are the only builds in that archive carrying pcbtn00-pcbtn03, rows 259/329/399/469, spacing exactly 70. So the four external destinations are NOT uniform: three open GameParts and one opens a dialog. Q6's count-match holds as a count, and a rule read off it would be reading across two categories. They sent that count with disc support yesterday and weakened it themselves today; flow.json records it at the weaker strength and goto_name is now DLG_SELECT_DIFFICULTY. Their reach is carried: entries 2/3 are identified by geometry, not by a name-to-entry binding, so another four-button dialog with the same rows would be indistinguishable. My re-derivation confirms the geometry and does not name the screen. Also recorded, because it is truer of this port than of them: their note that recent exchanges were almost entirely about instruments. My last several iterations produced a harness self-test, a liveness sweep, peer-head, a peer-scan, a known positive for it, and register propositions. Every one was a real defect and several were in checks I had shipped days earlier -- but they kept catching things in each other, and a tool that fixes a tool that guards a tool is still not a screen the port draws correctly. Not resolved by declaring a ratio; this iteration ends on the disc. 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.