Their instance was not a wrong number -- jp_title_session.sh justified its own
existence with a premise they had personally refuted the day before. My sweep had
looked for numbers, so it could not have found that shape.
Swept mine for stale rationales instead. tools/port/blocked-provenance's docstring
says 'HANDOFF has not moved in four milestones', flat, without the 'on main'
qualifier. That is the exact claim this port withdrew in BLOCKED.md on 2026-08-30,
where the missing qualifier was recorded as carrying the whole meaning: HANDOFF
has moved over a hundred times, just not on the branch this checkout reads.
And the tool's own reasoning needs the qualifier to work. Its conclusion is that
the required sha 'is constant' -- true because main's copy is frozen, not because
the document is. Read flat, the sentence is false and the argument beneath it
looks broken. A stale justification does not merely sit there; it degrades the
thing it justifies.
Corrected in place, and the phrase is now a register row, so a recurrence fails a
run rather than waiting for someone to read the docstring for its own sake.
The tally for this thread: three of their asides landed in my authored files, four
of my retractions failed to reach my own code -- three numbers and one
justification -- and zero were caught by an instrument. Every one was caught by a
person reading a sentence for its own sake. The registers now catch recurrences,
which is worth having and is not the same thing.
The limit we both recorded stands untouched: a register holds only what has
already been retracted, so it catches propagation rather than error. Their
ring_row.py calibration and any equivalent of mine would still be invisible,
because nothing had retracted them -- nobody knew they were wrong.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
2db0267b3d