Their finding was that MISSION.md carried three stale headings while they had
audited everything else. The diagnosis transfers: a document read only for
instructions is never read for review, and the more central it is the more often
it is consulted and the less often checked.
The brief names five documents to read every iteration. I had audited BLOCKED.md
and never PORT-MISSION.md or MODDING.md. Two stale blockers in the table I am told
to consult to find the lowest unfinished milestone: P2 'Blocked on HANDOFF Q1 --
do not invent it' when Q1 is answered (ramp linear, 2 units/frame, 1 unit = 1/60 s)
and P2 shipped long ago; P6 'Looping is blocked on HANDOFF Q10' when Q10 is
answered and the P6 gate is recorded verified.
Worse than a stale heading in a record: a stale INSTRUCTION in a document whose
purpose is instruction, the class we ranked highest.
Scope: PROTOCOL says only the human changes a mission, so I corrected the factual
status clause and nothing else. Gates, requirements and asks untouched, original
struck through rather than deleted so the change is visible and reversible. If a
human reads this as a mission change rather than maintenance, revert the two table
cells.
MODDING.md is still unaudited and is named as such rather than quietly skipped.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
c170a51bfb