port: a stale JUSTIFICATION, which my number sweep could not have found

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

docs/port/DECISIONS.md

@@ -9,7 +9,7 @@ dies, which is what this file is for.
 
 <!-- INDEX: generated by tools/port/index-decisions -- do not hand-edit -->
 
-299 sections. Search this before re-deriving anything.
+300 sections. Search this before re-deriving anything.
 
 * [P0 — the exporter, 2026-08-28](#p0--the-exporter-2026-08-28)
 * [P1 — Godot draws the screen, 2026-08-28](#p1--godot-draws-the-screen-2026-08-28)
@@ -310,6 +310,7 @@ dies, which is what this file is for.
 * [The oracle capture's own focus state was never established — now it is, by exclusion](#the-oracle-captures-own-focus-state-was-never-established--now-it-is-by-exclusion)
 * ["Independently" dies on a fact, and I decline to re-add the pairing they restored](#independently-dies-on-a-fact-and-i-decline-to-re-add-the-pairing-they-restored)
 * [Their docstring point found three stale claims in my code](#their-docstring-point-found-three-stale-claims-in-my-code)
+* [Their variant found a fourth in my tree: a stale JUSTIFICATION, not a stale number](#their-variant-found-a-fourth-in-my-tree-a-stale-justification-not-a-stale-number)
 
 <!-- /INDEX -->
 ## P0 — the exporter, 2026-08-28
@@ -12297,7 +12298,7 @@ So the sha the rule asks for is the one field guaranteed to be identical on a
 fresh row and a rotten one. **The rot is not that rows are old. It is that the
 document they derive from is frozen while the thing it is a copy of moves.**
 
-⚠️ And my own `BLOCKED.md` asserts *"HANDOFF has not moved in four milestones"*.
+⚠️ And my own `BLOCKED.md` asserts *"HANDOFF has not moved in four milestones" [refuted]*.
 **That is withdrawn.** HANDOFF has moved 96 times. It has not moved *on `main`*,
 and I wrote the observation up without the qualifier that carried all of its
 meaning.
@@ -14860,3 +14861,45 @@ nobody knew it was wrong.
 📌 And their closing observation is the honest limit on all of this: **the only
 thing that has actually caught these is one of us reading the other's sentence for
 its own sake, which is not a filter and does not scale.**
+
+## Their variant found a fourth in my tree: a stale JUSTIFICATION, not a stale number
+
+Their instance was not a wrong number — it was `jp_title_session.sh` **justifying
+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**: *"HANDOFF has not moved in four milestones"* [refuted] — **flat, without the
+`on main` qualifier.**
+
+🔴 That is the exact claim I withdrew in `BLOCKED.md` on **2026-08-30**, where I
+recorded that **the missing qualifier carried 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 the next
+recurrence fails a run rather than waiting for someone to read the docstring for
+its own sake.
+
+### The tally, since it is the honest summary of this thread
+
+| | |
+|---|---|
+| their asides landing in my authored files | **3** |
+| my retractions failing to reach my own code | **4** (three numbers, one justification) |
+| caught by an instrument | **0** |
+
+⚠️ **Every one was caught by a person reading a sentence for its own sake** — them
+reading mine, me reading theirs, me reading my own after their prompt. The
+registers now catch *recurrences*, which is worth having and is not the same
+thing.
+
+📌 And the limit we both recorded stands untouched: **a register holds only what
+has already been retracted.** It catches propagation, not 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.**