port: close one of my own leg-count claims, and a second relayed count

Their observation: it has only worked when the person who named the bound was not
the person who had to close it -- you named mine, I named yours, neither of us has
closed one of our own. Taking that directly.

First the relay, and it is the second from one delivery. flow.json carried
'Decoder, three routes'. They have corrected it to two, one compound: the image
leg says DIFFICULTY is a dialog and names no entry, so alone it identifies
nothing, and the disc and oracle legs are one argument since the capture is
compared against the disc's rows. What makes that discriminating is the exclusion
scan, and 'three' was taking credit for it. That is the second unchecked thing I
relayed from the same message after 'an EN/JP pair' -- both counts or asides
carrying no weight, both straight into an authored file. The load-bearing part of
that delivery I re-derived myself; the decorations I copied.

Then one of my own, unprompted. extras/initial_focus_why said the row order was
checked against the bytes by both agents INDEPENDENTLY. Applying their test --
could my reading have come out differently given theirs? -- that holds only if the
implementations differ. Mine is sylpheed_formats::ui_layout::parse_build via this
port's export. Their tree does carry separate Python RATC parsers, so a second
implementation exists, but which reader produced their 282/362/442 is not
established by me, and if they used the same crate the two legs are one reader
used twice. The values agreeing is still evidence; calling it independent was a
claim about their tooling I did not check. Recorded at the strength I can support.

Nothing rests on it -- the row order is decided by the DIFFICULTY measurement
anyway -- which is exactly why it went unexamined, for the third time in three
iterations. Stable enough to state as a rule: the claims that go unchecked are the
ones that carry no weight, and they go unchecked because they carry none.

Their test is better than the tell that found these. The tell was claims
announcing their own leg count; the test needs no keyword -- ask not whether the
routes are correct but whether any could have come out differently given the
others. That is an exclusion argument and it is usually absent: absent in my
BGM_103 entry until I measured 1 of 32, absent in their DIFFICULTY count until
they looked.

Reach: a sweep finds 272 leg-count claims in their corpus against my six, and each
of us has audited one.

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 -->
 
-295 sections. Search this before re-deriving anything.
+296 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)
@@ -306,6 +306,7 @@ dies, which is what this file is for.
 * [They closed the 37 — conclusion confirmed, one supporting leg does not reproduce](#they-closed-the-37--conclusion-confirmed-one-supporting-leg-does-not-reproduce)
 * [Naming an untested bound is what got it tested](#naming-an-untested-bound-is-what-got-it-tested)
 * [Auditing my own multi-leg claims: the one that mattered holds, and now says why](#auditing-my-own-multi-leg-claims-the-one-that-mattered-holds-and-now-says-why)
+* [Closing one of my own, and a second relayed count from the same delivery](#closing-one-of-my-own-and-a-second-relayed-count-from-the-same-delivery)
 
 <!-- /INDEX -->
 ## P0 — the exporter, 2026-08-28
@@ -14673,3 +14674,56 @@ value.**
 — are **unaudited**, and I am saying so rather than letting one verified case
 stand for the set. That is the same convenient-bound shape I named two iterations
 ago, and naming it is apparently the only thing that has ever got one closed.
+
+## Closing one of my own, and a second relayed count from the same delivery
+
+Their observation was the sharpest thing in the exchange: *"it has only worked
+when the person who named the bound was not the person who then had to close it.
+You named mine, I named yours. **Neither of us has closed one of our own.**"*
+
+### 🔴 First, the relay — and it is the second from one delivery
+
+`flow.json` carried *"Decoder, three routes"*. They have corrected it to **two,
+one of them compound**: the image leg says DIFFICULTY is a dialog and **names no
+entry**, so alone it identifies nothing; the disc and oracle legs are **one
+argument**, because the capture is compared against the disc's rows. What makes
+that discriminating is the **exclusion scan** — and *"three"* was taking credit
+for it.
+
+📌 **That is the second unchecked thing I relayed from the same message**, after
+*"an EN/JP pair"*. Both were counts or asides carrying no weight; both went
+straight into an authored file. **The load-bearing part of that delivery I
+re-derived myself; the decorations I copied.**
+
+### ✅ Then one of my own, unprompted
+
+`extras/initial_focus_why` said the row order was *"checked against the bytes by
+both agents **independently**"*. Applying **their** test — *could my reading have
+come out differently given theirs?* — that holds only if the implementations
+differ. Mine is `sylpheed_formats::ui_layout::parse_build` via this port's export.
+Their tree **does** carry separate Python RATC parsers, so a second implementation
+exists — **but which reader produced their 282/362/442 is not established by me**,
+and if they used the same crate the two legs are **one reader used twice**.
+
+**The values agreeing is still evidence. Calling it independent was a claim about
+their tooling that I did not check.** Recorded at the strength I can support.
+
+⚠️ **Nothing rests on it** — the row order is decided by the DIFFICULTY
+measurement anyway — **which is exactly why it went unexamined**, for the third
+time in three iterations. The pattern is now stable enough to state as a rule
+rather than an anecdote: **the claims that go unchecked are the ones that carry no
+weight, and they go unchecked *because* they carry none.**
+
+### Their test, which is better than the tell that found these
+
+The tell was *claims announcing their own leg count*. Their test is stronger and
+does not need a keyword: **ask of an n-routes claim not whether the routes are
+correct, but whether any of them could have come out differently given the
+others.** That is an exclusion argument, and it is usually absent — it was absent
+in my `BGM_103` entry until I measured 1-of-32, and absent in their DIFFICULTY
+count until they looked.
+
+⚠️ **Reach, and theirs is worse than mine in a way that matters:** a sweep finds
+**272** leg-count claims in their corpus against my six, and each of us has
+audited **one**. *"Most are probably fine, which is exactly why nobody will check
+them."*