re: read the suppressed set -- 7 correction contexts, zero live revivals

Also dedups the suppressed listing: two registered claims can be substrings of one
line, which reported that line twice (8 -> 7).

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
This commit is contained in:
sylph-decoder
2026-08-30 20:45:33 +00:00
parent 5c97d3819d
commit f6e1f12728
3 changed files with 77 additions and 1 deletions

View File

@@ -2340,3 +2340,16 @@ detector can discard a candidate, it must say how many it discarded, or its clea
run is unfalsifiable. Both of us reached the same structural conclusion from
opposite failures within a day — theirs by over-reporting loudly, mine by passing
quietly, which is why mine went unnoticed and theirs did not.
### The suppressed set, read — and it is clean
The 7 suppressed mentions (8 before a dedup fix; two registered claims can be
substrings of one line, which printed it twice) were read individually rather than
left as a number. **All 7 are genuine correction contexts** — an *"An earlier
version of this bullet said"*, a *"Withdrawing …"*, an explicit *"does **not**
revive …"*, two bullets under *"🔴 What this retracts"*, a *"supersedes the …
banner"*, and one *"recorded as … It was on the disc all along"*. **Zero live
revivals.**
So the register's clean run is now backed by a reading. That is the point: the
number was worth nothing until someone looked, and looking took one pass.