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

method: the plate glyph counter false-positives on the attract movie by 13x

Browse Source 
Found while controlling the timing probe before a settle_time run, not by
reasoning about it.

title_timing_probe.py s plate detector thresholds a green-glyph pixel count at
400, and its control checks two committed movie frames that both score 0. A real
boot disagrees: in one 100 s attract window, 17 frames scored at or above 400
and the peak was 5393. The attract movie has green content in the plate region.

The probe is not wrong -- its state machine refuses to look at the glyph until
the content classifier has already labelled the frame title_noplate or
title_plate, so the false positives never reach the drive. But it is safe
because of that gate, not because the threshold discriminates, and the
distinction matters for anyone reusing glyph() on its own.

Recorded with the general form: a two-frame control over a three-and-a-half
minute movie is not a control over that movie.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QsEPXWVaEpyfudtR6re1Pd
This commit is contained in:
sylph-decoder
2026-08-29 15:17:08 +00:00
parent ff715938f5
commit 82281df804
1 changed files with 9 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
docs/re/METHOD.md
View File

@@ -108,6 +108,15 @@ agent's loop prompt, i.e. nowhere durable. See [`README.md`](README.md) for the
* **"Animating" is not "still in a mission".**
* **Dedup entity enumerations by position value.**
* **Do not diagnose timing or liveness under gdb.** `ps %cpu` is cumulative.
* **The `PRESS Ⓐ` glyph counter false-positives on the attract movie by 13×.**
`title_timing_probe.py`'s plate detector thresholds a green-glyph pixel count
at 400, and its control checks two committed movie frames that both score 0.
A real boot disagrees: in one 100 s attract window, **17 frames scored ≥ 400
and the peak was 5 393** — the movie has green content in the plate region.
The probe is safe *because its state machine will not look at the glyph until
the content classifier has already said `title_*`*, not because the threshold
discriminates. ⚠️ **`glyph()` alone is not a plate detector**; a two-frame
control over a 3½-minute movie is not a control over that movie.
* **Classify screens by whole-image statistics, not named pixels** — a named
pixel is only valid while the image sits at a known place, and nothing errors
when it moves.