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

re: a .tbm DRAWS -- the TUTORIAL screen captured, and the 'inert' reading refuted

Browse Source 
Closes the open second reading in ui-forced-backdrop.md: that a .tbm contributes
no pixels, leaving 24 of its 62 deciding verdicts harmless rather than correct.

The TUTORIAL screen was reached and captured. It carries a full-screen blue
circuit/hex background. GP_TUTORIAL build 0's element 0 is pubase.tbm with pivot
(640,360) -- 1280x720, the only full-screen TEXTURED element in the bundle; the
one other full-screen element is pueff00.prm, an untextured primitive the colour
census puts at pure black. Our render of the same build is the identical layout
on pure black, 6.0-6.4 % inked against the game's 99.7 %. The only difference is
the background and the only thing it can be is the .tbm.

So the 24 .tbm verdicts are correct rather than harmless, and they are
load-bearing in the full sense. Reach: one .tbm observed; the class question is
settled, the ten other families are not individually seen.

Also: screen render is wrong on every screen carrying a .tbm -- it drops the
background silently, with no diagnostic.

And the identification is worth its own METHOD entry. Two statistical identifiers
were built. Masked correlation FAILED its control, picking EXTRAS over the known
main menu by 0.004 because the shared background dominates. A high-passed variant
PASSED by 1.28x, which is not a margin that licenses identifying an unknown, so it
was not used. The screen says TUTORIAL across the top. Ask whether the artefact
already states the answer before building a matcher.

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 10:53:34 +00:00
parent 77e54e95a5
commit ddc2a8e36b
3 changed files with 88 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

39
docs/re/structures/ui-forced-backdrop.md
View File

@@ -183,12 +183,39 @@ directly. It cannot be located:
capture covers a screen that has one (`GP_SAVE_LOAD`, `GP_BUNK`,
`GP_DEBRIEFING_PILOTLOG`), so nothing says whether the game draws any either.
⚠️ **So a second reading survives and is not excluded**: that a `.tbm` element
contributes no pixels, in which case its paint position is *inert* rather than
wrong. That would leave the 38 verdicts harmless instead of correct — a different
claim with the same consequence. Distinguishing them needs a capture of a screen
that carries one, which is behind the Ⓐ fault
([`ui-clock-freezes-at-settle.md`](ui-clock-freezes-at-settle.md)).
🔴 **REFUTED 2026-08-30 — a `.tbm` DRAWS, and the capture is now in hand.**
This paragraph used to say a second reading survived: that a `.tbm` contributes no
pixels, so its paint position is *inert* rather than wrong, leaving the verdicts
harmless instead of correct. **That reading is dead.**
The `TUTORIAL` screen was reached in the running game and captured
([`live-tutorial-screen.png`](../captures/title-builds/live-tutorial-screen.png)).
It carries a **full-screen blue circuit/hex background**. `GP_TUTORIAL` build 0 has
18 elements, and **element 0 is `pubase.tbm` with pivot (640, 360)** — 1280×720,
the only full-screen *textured* element in the bundle. The one other full-screen
element is `pueff00.prm`, an untextured primitive, and this page's own colour census
says every full-screen `*eff00*` primitive is **pure black**.
Our render of the same build
([committed beside it](../captures/title-builds/render-tutorial-build0-for-comparison.png))
is the **identical layout** — same title, same seven items, same footer — on **pure
black**: 6.0–6.4 % of the frame inked against the game's 99.7 %. The only difference
is the background, and the only thing that can be is the `.tbm`.
✅ **So the `.tbm` verdicts are CORRECT, not merely harmless.** They are load-bearing
in the full sense, and if the alpha-over assumption under this rule ever fails, those
24 deciders go with it for real.
⚠️ **Reach: one `.tbm`, `pubase.tbm`.** The other families —
`px_deb_base`, `px_bunk_base`, `pvbase`, `pqbase`, `pnbase`, `pjbgbase2`, `pcbase`,
`px_replay_base`, `px_movie_base`, `px_mission_base` — are not individually
observed. What is settled is the *class* question this paragraph posed: a `.tbm` is
not an element that draws nothing.
🔴 **And it means `screen render` is WRONG on every screen carrying a `.tbm`** — it
omits the background silently, with no diagnostic. That is a limitation of the
reference renderer, not of the game.
## 🔴 Stability is not necessity — 62 of the 80 are DECIDED by this rule (2026-08-30)