fabi/Sylpheed
1
0
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects Releases Wiki Activity

re: run 'grep the corpus for the claim' on this corpus -- four still standing

Browse Source 
Applying my own METHOD entry one iteration after writing it found four refuted
statements still asserted unmarked where a reader lands:

  * envelope correlation 'has no resolving power' -- in three places including
    HANDOFF. The port controlled the same estimator on a single track and got
    r=1.0000 at zero offset; the saturation needs CONCURRENT streams sharing
    timing. I agreed to this in a message and never landed it.
  * '8 of 10 three-chunk regions' -- still asserted in HANDOFF in a different
    section from its own correction.
  * 'r9 is a wild pointer, never a guest address' -- still asserted inside the
    kept-for-the-record section.
  * the ALSA channel permutation, stated without scope, when a later capture
    measured the identity and labelling from it put the silent channel on the
    wrong name.

All four marked in place, striking the sentence and pointing forward.

Two lessons added: a 'kept for the record' section still asserts, so labelling
the heading is not enough; and naming a refuted claim keeps it greppable, so the
audit returns its own corrections as hits and every hit needs reading.

The first item is the one worth admitting: I acknowledged that correction in a
message, wrote the entry about corrections that never land, and then did not land
my own for a full iteration.

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 10:35:27 +00:00
parent 3c55b1409b
commit 4cce44a64d
5 changed files with 66 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
docs/re/METHOD.md
View File

@@ -1482,3 +1482,31 @@ inside the emulator and looked exactly like a dead pad.
📌 Companion to the entry above about controls: a control proves your instrument
reads correctly; a **delivery check** proves the experiment happened at all. They
are different, and only the second one catches a null result that never ran.
### The audit, run on this corpus — and I had already re-offended
Applying *grep the corpus for the claim* to this repository, one iteration after
writing it, found **four** refuted statements still standing unmarked at the point
they are made:
| claim | where | refuted by |
|---|---|---|
| envelope correlation "has no resolving power" | 3 places, incl. `HANDOFF.md` | the port's control: r = 1.0000 at zero offset on a single track — the saturation needs *concurrent* streams |
| "8 of 10 three-chunk regions start mid-stream" | `HANDOFF.md`, in a *different* section from its correction | the completed census: 25 three-chunk, 17 affected |
| "`r9` is a wild pointer… never a guest address" | `HANDOFF.md`, in the kept-for-the-record section | it is a *host* address; subtract `0x100000000` |
| the ALSA channel permutation, stated without scope | `audio-capture-alsa-file-tee.md` | a later capture measured the **identity** |
🔴 **The first is the one worth admitting.** The port corrected that claim, I agreed
in a message, wrote the METHOD entry about corrections that never land — **and did
not land my own, for a full iteration.** Acknowledging a correction in
conversation feels like making it and is not.
📌 Two things the audit itself teaches:
* **A "kept for the record" section still asserts.** Labelling a section superseded
at its heading does not mark the sentence a reader lands on. Strike the sentence
and point forward from it.
* **Naming a refuted claim keeps it greppable**, so the audit returns its own
corrections as hits. Every hit needs reading, not just counting — a grep verdict
alone sends you to re-fix what is already fixed. That is the price of not deleting
the old sentence, and it is worth paying.