re: sweep my pre-fix numbers -- one real hit, durations survive, argument corrected

sylpheed-port asked which of my figures predate the keyframe record-layout fix,
noting the sharper form of the hazard: a fix that changes WHICH ROWS EXIST is
harder to sweep for than one that changes values, because the recomputation looks
like a correction rather than a different question.

Located the fix (5744f37, 2026-08-29 14:01) and enumerated docs quoting
keyframe-derived numbers that have not been touched since. One real hit:
structures/ui-group-start-time.md, a page about group START TIMES, written -- in
its own words -- "under the shifted time reading" and referring to the glows'
"untimed first keyframe".

Durations survive. The glow is visible ~0..45 (45 units) and the logo ~15..210
(195 units), exactly what its table already used; the "~0" it hedged with is now
a real timed 0.

The argument did not. It read "every glow declares the same times 15, 30, 45 ...
both families start at 15". Post-fix both start at 0, with times 0,15,30,45 and
0,15,30,190,194,206,210. Corrected in place with the original sentence quoted so
the change is visible.

The conclusion is unchanged and slightly stronger: on one clock the glow is
visible over 0..45 and the logo over 15..210, an overlap of 30 of the glow's 45
units, where the capture shows no overlap at all (glows frames 94-115, logos
116-211). A shared clock origin was contradicted before and is contradicted by a
wider margin now, because both groups demonstrably begin at the same declared
instant.

Of the three figures the port reports having quoted from me, the splash dwell
spans were already corrected today and the black-gap and cold-boot intervals are
capture-derived, so the fix does not reach them.

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 17:54:11 +00:00
parent 22846bf30e
commit 66c3422dec

View File

@@ -20,11 +20,37 @@ From the 235-frame draw capture of the developer splash, at the settled
in from their untimed first keyframe.) **Each element is on screen for its
declared span, to within 2 %.**
## ⚠️ Re-checked against the corrected reader, 2026-08-30 — durations survive, the argument needed fixing
This page was written **"under the shifted time reading"** — its own words — and
refers to the glows' *"untimed first keyframe"*. Both are pre-fix artifacts: the
[record-layout fix](../ui-keyframe-record-layout.md) (`a975517`, 2026-08-29 14:01)
times a group's final pose, and this page has not been touched since. Swept after
`sylpheed-port` asked which of my figures were computed before it. Post-fix:
```
palogo_gamearts.t32 0:a=0 15:a=0 30:a=255 190:a=255 194:a=232 206:a=32 210:a=0
palogo_gamearts_eff.t32 0:a=0 15:a=255 30:a=255 45:a=0
```
**The durations above are unaffected** — the glow is visible ≈0…45 (45 units)
and the logo ≈15…210 (195 units), which is exactly what the table already used.
The `~0` it hedged with is now a real, timed `0`.
## 🔴 But they do not share a clock origin
Every glow declares the same times — `15, 30, 45` — and every logo the same
`15, 30, 190, 194, 206, 210`. On one clock they would overlap almost entirely:
both families start at 15.
⚠️ **The original sentence here was pre-fix and is corrected.** It read: *"Every
glow declares the same times — `15, 30, 45` — and every logo the same `15, 30,
190, 194, 206, 210`. On one clock they would overlap almost entirely: both
families start at 15."* Post-fix **both families start at `0`**, and the times are
`0, 15, 30, 45` and `0, 15, 30, 190, 194, 206, 210`.
📌 **The conclusion is unchanged and slightly stronger.** On one clock the glow is
visible over units 0…45 and the logo over 15…210 — an overlap of 30 of the glow's
45 units. Measured, they overlap **not at all**: glows on frames 94115, logos
116211, the logos starting the frame after the glows end. A shared origin was
contradicted before and is contradicted by a wider margin now, because both groups
demonstrably begin at the same declared instant.
**They do not overlap at all.** The glows run frames **94115** and the logos
**116211** — strictly sequential, the logos starting the frame after the glows