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

re: reconcile the 49.6/92.3 split -- same numerator, and my explanation of it was wrong

Browse Source 
sylpheed-port reconciled the population gap exactly and I reproduced it: filtering
max_t > 0 gives 1781 records and 92.3 %, their figures precisely. Same numerator,
1643, both ways.

My stated explanation was wrong. I said the scan requires a timed keyframe; it does
not, because .max() returns Some(0) rather than None for records whose keyframes are
all at time 0, so 1530 records where the question has no content stayed in my
denominator and counted as failures by construction.

The conclusion is untouched -- +0x04 is 0 % under either denominator.

Records their diagnosis of why it stayed invisible: the numerator agreed to the
unit, so a shared 1643 read as agreement and neither of us looked there. And both
halves needed a qualifier neither carried -- 92.3 % is of the records where the
question is meaningful, not of nested records.

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-31 03:57:21 +00:00
parent 73c2b31e1b
commit e6a9d372f3
3 changed files with 48 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
docs/re/METHOD.md
View File

@@ -3235,3 +3235,26 @@ does not transfer to a per-record header: **an interior consistency check is
satisfied by any reading that is internally consistent — and "internally
consistent" is what a wrong offset into a regular structure usually is.** The
boundary rule is the special case where the structure's edges break that regularity.
## A denominator mismatch hides behind an agreeing numerator
Two agents, one statistic, and the disagreement was **entirely in the denominator**:
`1643/1781 = 92.3 %` against `1643/3311 = 49.6 %`. **Neither of us was wrong about
the disc.**
🔴 **My explanation of the gap was wrong too.** I said my scan "requires a timed
keyframe". It does not — `.max()` over the keyframe times returns `Some(0)`, not
`None`, for a record whose keyframes all sit at time 0, so those never left my
denominator. 1 530 records where *"does the word equal the largest keyframe time?"*
has **no content** were counted as failures **by construction**.
📌 **`sylpheed-port`'s diagnosis of why it stayed invisible is the transferable
part: the numerator agreed to the unit.** We both looked at **1 643** and neither
noticed we were dividing it differently. An agreeing numerator reads as agreement,
and a shared number is the last place either party looks for a discrepancy.
⚠️ **Both halves needed a qualifier neither carried.** 92.3 % is *of the records
where the question is meaningful*, not *of nested records* — quoted bare on both
sides for two days, including into a shipped doc comment. **A population-scoped
statistic reported without its population is the same shape as a negative reported
without its reach**, and this corpus already had a rule for the second.