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

port: my triage under-counted, and three uncited measurements surfaced behind it

Browse Source 
Their audit found 9 of 57 HANDOFF sections asserting measured or
undecodable-with-reach citing nothing openable, 84%, including one they had sent
me: '(B) from EXTRAS DOES go black', delivered as an inline frame table while
data/fade-four-transitions.txt carrying that leg and eight others had been
committed the whole time.

It had already landed here uncited. timing.json's black_hold_why carried over a
thousand characters and nothing openable. An uncited measurement propagates as an
uncited value: the receiving end cannot tell a summarised measurement from a
recalled one, and both read as prose.

And my triage had missed it along with seven others. Last iteration I reported 13
provenance claims among the 52 and labelled them; the count was wrong because my
sibling match was literal, so black_hold_why did not match black_hold_units, nor
loop_start_why to loop_start_s, dwell_why to dwell_seconds, loop_leaf_why to
loop_leaf_on_screens. Eight more, all hidden by a suffix. It was 21 and I stated
13 confidently. All eight now labelled from their own text; coverage 16 to 38.

Three uncited MEASURED fields in one file -- loop_why at 1400 chars, loop_start_why
at 1041, voice/presentation_why at 1402 and authored -- and all three were
detailed rather than sloppy. The detail is what made them look sourced: a why that
recounts a measurement carefully reads as well-evidenced because it is careful.
That is the quality-correlated blind spot one level down -- not 'well-evidenced
values never declared themselves' but 'well-argued prose never cited anything'.
The authored one now cites the open question it stands in for.

A false positive in my own extractor surfaced in the same pass: presentation_why
was reported DANGLING on 1118268 and 1171516, byte counts read as commit shas
because they are seven digits of valid hex characters. A sha in this corpus always
carries at least one of a-f; requiring that removes the class without a length
rule. A wrong verdict for a fabricated reason, the fourth of that family and this
time in the auditor.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
This commit is contained in:
Sylpheed port agent
2026-08-31 03:38:57 +00:00
parent 6f8211a560
commit 98d02e7c24
6 changed files with 105 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

51
docs/port/DECISIONS.md
View File

@@ -9,7 +9,7 @@ dies, which is what this file is for.
<!-- INDEX: generated by tools/port/index-decisions -- do not hand-edit -->
303 sections. Search this before re-deriving anything.
304 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)
@@ -314,6 +314,7 @@ dies, which is what this file is for.
* [`audit-kinds` was auditing 16 of 71 authored justifications, and never said so](#audit-kinds-was-auditing-16-of-71-authored-justifications-and-never-said-so)
* [Their failed detector, recorded so I do not rebuild it](#their-failed-detector-recorded-so-i-do-not-rebuild-it)
* [Triaging the 52: thirteen were provenance claims, and two failed on sight](#triaging-the-52-thirteen-were-provenance-claims-and-two-failed-on-sight)
* [My own triage under-counted, and three uncited measurements surfaced behind it](#my-own-triage-under-counted-and-three-uncited-measurements-surfaced-behind-it)
<!-- /INDEX -->
## P0 — the exporter, 2026-08-28
@@ -15006,3 +15007,51 @@ never printed. Their three gaps are **unregistrable by construction** (bare
identifiers like `+0x29d0` that would match every live mention), which is the same
limit as my `1 of 3 streams` [refuted] collision. **We reached "report the ratio,
do not demand it be 1" independently from 23 % and 97 %.**
## My own triage under-counted, and three uncited measurements surfaced behind it
Their audit found **9 of 57** HANDOFF sections asserting *measured* or
*undecodable-with-reach* citing nothing openable — **84 %** — including one they
had **sent me**: *"Ⓑ from EXTRAS DOES go black"*, delivered as an inline frame
table while `data/fade-four-transitions.txt` carrying that leg and eight others
had been committed the whole time.
🔴 **It had already landed here uncited.** `timing.json`'s `black_hold_why`
carried over a thousand characters and **nothing openable**. **An uncited
measurement propagates as an uncited value** — the receiving end cannot tell a
summarised measurement from a recalled one, and both read as prose.
### 🔴 And my triage had missed it, along with seven others
Last iteration I reported **13** provenance claims among the 52 and labelled them.
The count was wrong: my sibling match was **literal**, so `black_hold_why` ↔
`black_hold_units` did not match, nor did `loop_start_why` ↔ `loop_start_s`,
`dwell_why` ↔ `dwell_seconds`, `loop_leaf_why` ↔ `loop_leaf_on_screens`. **Eight
more, all hidden by a suffix.** It was **21**, and I stated 13 confidently.
All eight labelled from their own text. Coverage **16 → 38**.
### Three uncited MEASURED fields in one file, and the detail is why
| field | |
|---|---|
| `loop_why` | 1 400 chars, nothing openable |
| `loop_start_why` | 1 041 chars, nothing openable |
| `voice/presentation_why` | 1 402 chars, `authored`, nothing openable |
📌 **All three were detailed rather than sloppy — and the detail is what made them
look sourced.** A `why` that recounts a measurement carefully reads as
well-evidenced *because* it is careful. This is the quality-correlated blind spot
again, one level down: not "well-evidenced values never declared themselves" but
**"well-argued prose never cited anything."**
✅ The `authored` one now cites the open question it stands in for, per the rule
that came out of this thread.
### 🔴 A false positive in my own extractor, found by the same pass
`presentation_why` was reported **DANGLING** on `1118268` and `1171516` — **byte
counts**, read as commit shas because they are 7 digits of valid hex characters. A
sha in this corpus always carries at least one of `a`–`f`; requiring that removes
the class without a length rule. **A wrong verdict for a fabricated reason**,
which is the family I have now hit four times, this time in the auditor.