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

re: break the EXTRAS n=1 cap -- which I had wrongly called structural

Browse Source 
I recorded EXTRAS as able to supply only one gap measurement because "its sole
exit is (B) to the menu", and called that n=1 STRUCTURAL -- a word that retires a
question. The disc refutes it in one command: build 6 declares three buttons,
ptbtn11/ptbtn12/ptbtn13, all kind 0x3002. The cap was an unverified assertion I
had already written into HANDOFF twice.

Measured EXTRAS -> a screen outside GP_TITLE via (A): outgoing quad rises across
frames 36-40 (4-5 frames, matching build 6's declared 10-unit close), then THREE
empty frames at 42, 43, 44, then a different archive builds (23-28 draws/frame
against GP_TITLE's 11-14). Gap = 3.

So EXTRAS as outgoing gives {2, 3}, and seven transitions now group as:
menu {0,1,1} n=3, EXTRAS {2,3} n=2, title {3,3,3} n=3.

A pairwise control that holds the destination class constant: menu -> another
archive gives 1, EXTRAS -> another archive gives 3. Same kind of destination, gap
differs by outgoing screen. That is the strongest support yet for the
outgoing-screen dependence because it removes the destination as the variable.

But the clean ordering is GONE: EXTRAS {2,3} and title {3,3,3} overlap at 3, so
"menu < EXTRAS < title" no longer separates them. What survives is weaker -- the
outgoing screen constrains the gap to a ~2-wide band and the bands are not
disjoint.

METHOD: a structural limit is a claim and needs checking like any other.
"Structural" and "impossible" are the two words most worth distrusting in your own
notes, because they retire a question rather than answering it and nothing later
re-opens 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 18:49:29 +00:00
parent e823cfe6fa
commit cd829b6dad
4 changed files with 75 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
tools/re-capture/fade_decompose.sh
View File

@@ -101,7 +101,7 @@ elif [ "$WHERE" = "menu2other" ]; then
shot "$OUT/armed-on-menu.png"
echo " arming on: $(python3 "$SD/which_title_screen.py" "$OUT/armed-on-menu.png")"
BTN=A
elif [ "$WHERE" = "extras" ] || [ "$WHERE" = "menu2extras" ]; then
elif [ "$WHERE" = "extras" ] || [ "$WHERE" = "menu2extras" ] || [ "$WHERE" = "extras2other" ]; then
BRANCH="extras-family: navigate to EXTRAS"
python3 "$SD/pad.py" tap A 0.5
for _ in 1 2 3 4 5 6; do
@@ -144,6 +144,14 @@ elif [ "$WHERE" = "extras" ] || [ "$WHERE" = "menu2extras" ]; then
echo " back on menu: $(python3 "$SD/which_title_screen.py" "$OUT/back-on-menu.png")"
BTN=A
BRANCH="menu2extras: back on the MENU with focus restored -> press (A)"
elif [ "$WHERE" = "extras2other" ]; then
# A SECOND value for EXTRAS as the outgoing screen. I had recorded EXTRAS as
# having a sole exit -- (B) to the menu -- and called its n=1 STRUCTURAL. The
# disc refutes that: build 6 declares three buttons, ptbtn11/12/13, all kind
# 0x3002. So (A) on EXTRAS leaves it by a different route and the cap was an
# unverified assertion, not a property of the archive.
BTN=A
BRANCH="extras2other: arm on EXTRAS -> press (A), leaving by a button"
else
BTN=B
BRANCH="extras: arm on EXTRAS -> press (B)"