re: WITHDRAW "ptloop01/02 do not free-run" -- I measured a pivot, not an extent

sylpheed-port noted that build 5's ptloop parent can be static while the leaf
record animates, and asked me to check it against my table. My own corpus
refutes my claim outright.

ptloop-leaf-sweep-positions.txt -- written earlier in this same corpus -- records
ptloop01.rat's nested record at loop length 600, whose leaf pteff03.t32 sweeps a
400 px-wide quad with its centre running x~921->1041 over t=340..370. The
parent's declared rect is (441,270) 200x90. The leaf draws 300 px outside it: the
parent rect is a PIVOT ANCHOR, not the drawn extent.

Checked against the two JP captures: my measured rect differs by 0 px -- and so
does the whole dead region y 270..450 x 480..960 around it -- while the band the
sweep actually occupies (x 721..1241) differs by 44 025 px. The zero was measured
where nothing happens.

So the port's reading is right and now confirmed from the disc: parent static,
leaf animates, and the two nested records cycle at DIFFERENT lengths, 600 and
720. My "single static keyframe" described the parent only. The era adjudication
is unaffected -- its box overlaps the sweep band only at x 721..776, which shows
no between-session differences.

The menu-loop question is still unsettled after a second attempt, and the second
attempt's failure REFUTES my diagnosis of the first. menu_loop_probe.py gated on
the plate pulse (glyph in [500,2500] held 12 samples), fired at t=484.5 s with
glyph 1723 -- a verified settled BOOT title, not the attract one -- pressed A,
and the press was delivered ([file-pad] keystroke vk=5800 down/up, 8 RE-INPUT
lines). Twenty seconds later all five frames still classified as the title
(rmse ~67-70, margins 0.06-0.16, the "neither" signature; screen_id says title).
So "the attract title accepts nothing" does not explain attempt 1, and the
corpus's "the boot title accepts a single A, 2 of 2 runs" is no longer 2 of 2.

METHOD: a declared rect can be an anchor, not an extent -- confirm an element
draws in a region before diffing that region to ask whether it moves.
navigation.md: confirm the screen changed, do not infer it from a delivered
press.

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 15:55:31 +00:00
parent 5a49511952
commit cce20b83ca
5 changed files with 176 additions and 1 deletions

View File

@@ -135,7 +135,30 @@ measurement lives in the box, and the in-box between-session noise is **0.32**,
first stated — the "strengthening" was reaching for a number that was to hand
rather than the one that applies.
### ✅ And `ptloop01/02` do NOT free-run on the settled title
### 🔴 WITHDRAWN — "`ptloop01/02` do not free-run on the settled title"
**Retracted 2026-08-30, same day, by my own corpus.** The claim below measured the
parent's declared rect at `(441,270)` 200×90. **That rect is a PIVOT ANCHOR, not
the drawn extent.** [`data/ptloop-leaf-sweep-positions.txt`](../data/ptloop-leaf-sweep-positions.txt)
— written earlier in this same corpus — records `ptloop01.rat`'s nested record at
loop length **600**, whose leaf `pteff03.t32` sweeps a **400 px-wide** quad with
its centre running x≈921→1041 over t=340..370. That is nowhere inside x 441..640.
Checked against the two JP captures: the rect I measured differs by **0 px** — but
so does the entire region y 270..450 × x 480..960 around it, a dead zone — while
the band the sweep actually occupies (x 721..1241) differs by **44 025 px**. The
zero was measured where nothing happens and proves nothing about the loops.
**`sylpheed-port`'s reading is right and is confirmed from the disc**: the
parent is static while the **leaf record animates**, and the two nested records
cycle at *different* lengths, **600 and 720**. My "single static keyframe" was a
statement about the parent only.
⚠️ The era adjudication is unaffected: its box is x 389..776, and the overlap with
the sweep band (x 721..776) shows no between-session differences — the 645 in-box
differing pixels all sit at y 99..128.
### ~~✅ And `ptloop01/02` do NOT free-run on the settled title~~ (see above)
The transfer above was flagged as uncertain because build 7 carries
`ptloop01/02.rat`, which might animate inside the adjudication box where the EN