The 1.7x/3.2x title-clock conflict I was carrying as an open doubt against every unit-valued figure on the title was never a conflict: the Decoder had been applying the plate's declared ramp to ptcopyright. One mislabelled element generated the whole discrepancy. Same shape as the port gating a snap on settle_instant while reading a printed number that came from settle_time(). Two elements, one label. In both cases what caught it was measuring a RATIO, which needs no identification, rather than a value, which does. rate 0.5 now rests on three declared quantities that agree, the third unrelated to the first: ptloop01's 30-unit ramp, the leaf's 600-unit loop, and ptbtn00f's pulse at exactly 1/10 of that loop (60.0 frames over 16 cycles, zero variance). Also recorded: the plate's pulse is now measured -- ptbtn00f, 120 title units, peak alpha 80, drawn 51 of 60 frames. NOT implemented: the plate's blink is neither F5 nor F6, and the human's standing note is that its delay is accepted.
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.