From 2a338ad2e23b86867b8f03ae6c5e012ea43c880d Mon Sep 17 00:00:00 2001 From: Sylpheed port agent Date: Sun, 30 Aug 2026 13:22:11 +0000 Subject: [PATCH] port: audit my tree for the disc-wide ordinal foot-gun -- no exposure, verified The Decoder found the ordinal/entry divergence is disc-wide (21 of 24 archives, 18 at ordinal 0) and that GP_TITLE is the mildest case on the disc, the only archive whose first ten ordinals are the identity. That is luck, not design. No exposure here, checked: the four archives they flag appear in flow.json with no numbers at all, screen_names.json already says LOCATED BY ENTRY INDEX, and every tool of mine passes --all. Verified the high ordinals where GP_TITLE's identity would break first, since my export addresses 13 and 14: publisher twins 10 vs 13 at RMSE 3.06, developer twins 11 vs 14 at 4.33, against a control of 47.91 for two genuinely different screens. The addressing lands where HANDOFF says the entries are, and the control shows a mismatch would have been caught. The constraint is recorded for whoever exports those four archives; the absence of exposure is a fact about what I have exported, not a property of the tooling. Also corrects my own wording: I called ptlogo_all_eff a '50% glow'. What is measured is the plateau -- that it is a glow rests on kind 0x3000 and a 200% scale that nobody has put in front of the running game. The mid-ramp correction stands on the numbers alone. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF --- docs/port/DECISIONS.md | 53 +++++++++++++++++++++++++++++++++++++++++- 1 file changed, 52 insertions(+), 1 deletion(-) diff --git a/docs/port/DECISIONS.md b/docs/port/DECISIONS.md index f92030a0..f69b48f6 100644 --- a/docs/port/DECISIONS.md +++ b/docs/port/DECISIONS.md @@ -9,7 +9,7 @@ dies, which is what this file is for. -158 sections. Search this before re-deriving anything. +159 sections. Search this before re-deriving anything. * [P0 — the exporter, 2026-08-28](#p0--the-exporter-2026-08-28) * [P1 — Godot draws the screen, 2026-08-28](#p1--godot-draws-the-screen-2026-08-28) @@ -169,6 +169,7 @@ dies, which is what this file is for. * [My own predictor holds — and the evidence that made it *better than width* does not](#my-own-predictor-holds--and-the-evidence-that-made-it-better-than-width-does-not) * [Checking my own tree for the ordinal foot-gun that just voided three of theirs](#checking-my-own-tree-for-the-ordinal-foot-gun-that-just-voided-three-of-theirs) * [Looking for a case that separates width from mid-ramp — there is none, and I nearly invented one](#looking-for-a-case-that-separates-width-from-mid-ramp--there-is-none-and-i-nearly-invented-one) +* [Auditing my tree for the disc-wide ordinal foot-gun](#auditing-my-tree-for-the-disc-wide-ordinal-foot-gun) ## P0 — the exporter, 2026-08-28 @@ -9181,3 +9182,53 @@ construction* one that closes while things are still moving. Decoder I had found the separating case and asking them to act on it — and the thing that flagged it was reading the keyframes of the single element the claim rested on. **The screen most useful to me was the one I checked least.** + +## Auditing my tree for the disc-wide ordinal foot-gun + +The Decoder found the ordinal/entry divergence is disc-wide — 21 of 24 +build-bearing archives, 18 diverging at ordinal 0 — and that **`GP_TITLE` is the +mildest case on the disc**, the only archive whose first ten ordinals are the +identity. That is the whole reason this corpus survived, and it is luck, not +design. + +✅ **No exposure in my tree, checked rather than assumed.** + +* The four archives they flag as exposed — `GP_READY_ROOM`, `GP_HANGAR_ARSENAL`, + `GP_MISSION_SELECT`, `GP_OPTIONS` — appear in `authored/flow.json` with **no + numbers at all**, only as *"not in this export"*. Nothing to misread. +* `authored/screen_names.json` already says **"LOCATED BY ENTRY INDEX, not by a + rule"** — the exact disambiguation their second warning asks for. +* Their second point (`--all` swaps the predicate, so `--build N` and + `--build N --all` are different objects) is what `verify-screen`'s header + already relies on, and every tool of mine passes `--all`. + +### Verifying the high ordinals, where GP_TITLE's luck would run out first + +The identity holds for the first ten ordinals. My export addresses **13** and +**14**, past that point, so the interesting test is up there: + +| | RMSE | | +|---|---|---| +| `publisher_logo` (10) vs `publisher_logo_r` (13) | **3.06** | region twins — near-identical ✅ | +| `developer_logos` (11) vs `developer_logos_r` (14) | **4.33** | region twins — near-identical ✅ | +| `publisher_logo` (10) vs `developer_logos` (11) | **47.91** | different screens — control, 11–16× worse | + +✅ `--build N --all` lands exactly where HANDOFF says entries 10/13 (publisher) and +11/14 (developer) are, across the full range where divergence could begin, and the +control shows the test would have caught a mismatch. + +⚠️ **The constraint is recorded for whoever exports those four archives**, which is +not this port today: `--build 0` is not entry 0 in any of them. The current +absence of exposure is a fact about what I have exported, not a property of the +tooling. + +### A precision correction to my own wording + +They tried to refute my `ptlogo_all_eff` correction and could not — the quote is +exact and `a=127` holds flat across 134 units with position and scale constant. + +⚠️ But they flag something I should not have said. I called it a *"50 % glow"*. +**What is measured is the plateau**; that it *is* a glow rests on kind `0x3000` +and a 200 % scale, and nobody has put that in front of the running game. The +correction to my mid-ramp test stands on the numbers alone and needs no reading of +what the element depicts — which is how it should have been written.