Both are the one-hop failure the amendment itself is largely about -- the
correction reached the top of each file and stopped.
CONTRACT_P13S16_PROJECTION.md
The status block was moved to LANDED / RESOLVED, but two screens below it the
ratification-time framing still read "not the fourth", "nothing is
implemented", "every gate, test and mutation is specified and none has been
run", and "4a's landing obligation is outstanding by construction". A reader
scrolling past the status line met the pre-execution contract presented as
current.
Everything from that point to 7 is now marked as a DATED RECORD, S27-style:
retained rather than rewritten, because the pins are frozen and the review
records are the review state. The four "what ratification does NOT settle"
bullets keep their text and gain their outcomes -- t9 confirmed, t8d
falsified, all gates and mutations run, 4a honoured then discharged at
3328b2c, and the predicted post-execution amendments being this one.
EVIDENCE_P13S16_EXECUTION.md
Its header still said it was "deliberately not staged", absent from the touch
table, and that committing it would need an amendment adding a touch row --
describing, in the present tense, the state the commit it arrived in had just
ended. Recast to past tense, pointing at 7's touch row 12.
The distinction it was drawing survives and is kept: the fourteen paths in
aee4ff9 are the rung, this is the evidence the rung was reviewed against. It
documents aee4ff9; it is not part of it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Ps1szk2mSfgp4Cz21eVH9x
Levi Neuwirth
fcc3fb6b39