6cdffd8f77
The work my own measurement said was needed: a legacy residue, not a new
discipline. Doing it corrected the number twice.
First, '17 uncited' was inflated by my own extractor. Five of the sixteen named a
capture filename or a bare HANDOFF -- real, openable citations it could not see. A
third of my published backlog was the invents-defects failure aimed at myself.
Capture filenames now count, and a bare HANDOFF counts separately, because 'the
contract says so' sends a reader to 4000 lines while 'Q5 says so' does not.
Then the genuine twelve, all backfilled to zero. The plate-overlay group cites
plate-pulse-measured.md, plate-pulse-phase-lock.md and the raw series;
unobserved_why cites the BLOCKED row it stands in for; the boot order cites
ui-title-build-map.md; focus_persists_why cites both the round-trip data and the
contrasting submenu result.
screen_names.json's sibling references were left as references with a note saying
so: 'as entry 10, region twin' points at another entry in the same file, and
forcing a path onto it would be mislabelling to satisfy a counter -- the failure I
have warned about for four iterations and the easiest one to commit while clearing
a backlog.
Their dialog record layout was wrong and I had copied it. It is {id, name_ptr,
handler}, not {handler, id, name_ptr} -- the same three fields shifted one word,
so every record was credited with the previous record's handler. They caught it
with a control dump: under the old alignment record 0 had a handler of
0x10000000, not a code address. ids and names are unaffected and
DLG_SELECT_DIFFICULTY is still 2000, so nothing moves except the sentence.
Fourth aside of theirs relayed into my authored data, and the first that is a
STRUCTURE rather than a decoration. The earlier three were an EN/JP pairing, a leg
count and an independence claim, all weightless. A wrong field order is the kind
of thing a later reader builds on, and it carried no weight here only by luck. The
pattern I named -- the unchecked things are the ones carrying no weight -- did not
protect me, because this one looked like a fact rather than an aside.
Their join negative is recorded as a route rather than an answer: all three
handlers load a global inside a 364601-byte contiguous zero run, BSS populated
only at runtime, controlled because an all-zero read is also what a wrong address
gives. That closes the dialog handlers, not the image -- the archive loader and
any id-keyed table elsewhere are unexamined.
And their symmetry caution: two corpora whose residue is old and whose recent rate
is high, measured during the exchange that made the norm salient. Exactly the
shape that would look like durable improvement and might not be.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
95 lines
12 KiB
JSON
95 lines
12 KiB
JSON
{
|
|
"format": "sylpheed.screen_names/1",
|
|
"_": [
|
|
"Which GP_TITLE pak entry is which screen. AUTHORED: the disc does not name its",
|
|
"builds, so every name here is a decision. The identifications come from",
|
|
"HANDOFF Q2 (ui-title-build-map.md), which measured them against framebuffer",
|
|
"captures of the running game; the exporter stamps the name into the screen",
|
|
"file with name_source: \"authored\" so a reader can tell a recovered name from",
|
|
"an invented one.",
|
|
"",
|
|
"KEYED BY PAK ENTRY INDEX, not by the enumeration ordinal. It used to be the",
|
|
"ordinal; widening the enumeration to reach the splash renumbers ordinals, and",
|
|
"a name that moves when the enumeration rule changes is not a name. The entry",
|
|
"was always described here as the stronger locator -- now it is the only",
|
|
"stable one.",
|
|
"",
|
|
"Delete an entry here the day the RE agent decodes a name field."
|
|
],
|
|
"archives": {
|
|
"dat/GP_TITLE.pak": {
|
|
"2": {
|
|
"name": "press_start",
|
|
"why": "HANDOFF Q2: builds 2/3 are the PRESS (A) BUTTON plate -- a build of its own, composited over the title and faded in a beat later. English of the EN/JP pair. Measured against a live capture. 📌 SOURCE, added 2026-09-01 in the uncited-why backfill: the four bundles are identified in docs/re/ui-title-build-map.md, and the ordinal-versus-entry distinction this entry depends on is docs/re/structures/build-ordinal-vs-entry.md. ⚠️ The sibling references below (\"as entry 10, region twin\") are a citation form too -- they point at another entry in this file rather than at a document, and forcing a path onto them would be mislabelling to satisfy a counter."
|
|
},
|
|
"3": {
|
|
"name": "press_start_jp",
|
|
"why": "HANDOFF Q2: the Japanese twin of build 2. Out of scope for this milestone; named so it is not mistaken for a screen we need. 📌 SOURCE, added 2026-09-01 in the uncited-why backfill: the four bundles are identified in docs/re/ui-title-build-map.md, and the ordinal-versus-entry distinction this entry depends on is docs/re/structures/build-ordinal-vs-entry.md. ⚠️ The sibling references below (\"as entry 10, region twin\") are a citation form too -- they point at another entry in this file rather than at a document, and forcing a path onto them would be mislabelling to satisfy a counter."
|
|
},
|
|
"4": {
|
|
"name": "title",
|
|
"why": "HANDOFF Q2: build 4 is the English title art. Measured against a live capture. 📌 SOURCE, added 2026-09-01 in the uncited-why backfill: the four bundles are identified in docs/re/ui-title-build-map.md, and the ordinal-versus-entry distinction this entry depends on is docs/re/structures/build-ordinal-vs-entry.md. ⚠️ The sibling references below (\"as entry 10, region twin\") are a citation form too -- they point at another entry in this file rather than at a document, and forcing a path onto them would be mislabelling to satisfy a counter."
|
|
},
|
|
"5": {
|
|
"name": "main_menu",
|
|
"why": "HANDOFF Q2: builds 5/8 are the five-button main menu; 5 is English. Measured against a live capture. (An earlier reading called 8 a submenu and was withdrawn -- 8 is the Japanese main menu.) 📌 SOURCE, added 2026-09-01 in the uncited-why backfill: the four bundles are identified in docs/re/ui-title-build-map.md, and the ordinal-versus-entry distinction this entry depends on is docs/re/structures/build-ordinal-vs-entry.md. ⚠️ The sibling references below (\"as entry 10, region twin\") are a citation form too -- they point at another entry in this file rather than at a document, and forcing a path onto them would be mislabelling to satisfy a counter."
|
|
},
|
|
"6": {
|
|
"name": "extras",
|
|
"why": "HANDOFF Q2: builds 6/9 are the EXTRAS submenu, the only submenu inside this archive. Measured against a fresh EXTRAS capture. 📌 SOURCE, added 2026-09-01 in the uncited-why backfill: the four bundles are identified in docs/re/ui-title-build-map.md, and the ordinal-versus-entry distinction this entry depends on is docs/re/structures/build-ordinal-vs-entry.md. ⚠️ The sibling references below (\"as entry 10, region twin\") are a citation form too -- they point at another entry in this file rather than at a document, and forcing a path onto them would be mislabelling to satisfy a counter."
|
|
},
|
|
"7": {
|
|
"name": "title_jp",
|
|
"why": "HANDOFF Q2: the Japanese twin of build 4. 📌 SOURCE, added 2026-09-01 in the uncited-why backfill: the four bundles are identified in docs/re/ui-title-build-map.md, and the ordinal-versus-entry distinction this entry depends on is docs/re/structures/build-ordinal-vs-entry.md. ⚠️ The sibling references below (\"as entry 10, region twin\") are a citation form too -- they point at another entry in this file rather than at a document, and forcing a path onto them would be mislabelling to satisfy a counter."
|
|
},
|
|
"8": {
|
|
"name": "main_menu_jp",
|
|
"why": "HANDOFF Q2: the Japanese twin of build 5. 📌 SOURCE, added 2026-09-01 in the uncited-why backfill: the four bundles are identified in docs/re/ui-title-build-map.md, and the ordinal-versus-entry distinction this entry depends on is docs/re/structures/build-ordinal-vs-entry.md. ⚠️ The sibling references below (\"as entry 10, region twin\") are a citation form too -- they point at another entry in this file rather than at a document, and forcing a path onto them would be mislabelling to satisfy a counter."
|
|
},
|
|
"9": {
|
|
"name": "extras_jp",
|
|
"why": "HANDOFF Q2: the Japanese twin of build 6. 📌 SOURCE, added 2026-09-01 in the uncited-why backfill: the four bundles are identified in docs/re/ui-title-build-map.md, and the ordinal-versus-entry distinction this entry depends on is docs/re/structures/build-ordinal-vs-entry.md. ⚠️ The sibling references below (\"as entry 10, region twin\") are a citation form too -- they point at another entry in this file rather than at a document, and forcing a path onto them would be mislabelling to satisfy a counter."
|
|
},
|
|
"10": {
|
|
"name": "publisher_logo",
|
|
"why": "The SQUARE ENIX PUBLISHER wordmark -- the FIRST thing the boot sequence shows, before the developer logos. Measured by the RE agent 2026-08-29, render grid at docs/re/captures/title-builds/splash-both-halves-rendered.png. Entries 10/13 are region twins distinguished by the trademark glyph; 10 carries the (TM). 📌 SOURCE, added 2026-09-01 in the uncited-why backfill: the four bundles are identified in docs/re/ui-title-build-map.md, and the ordinal-versus-entry distinction this entry depends on is docs/re/structures/build-ordinal-vs-entry.md. ⚠️ The sibling references below (\"as entry 10, region twin\") are a citation form too -- they point at another entry in this file rather than at a document, and forcing a path onto them would be mislabelling to satisfy a counter."
|
|
},
|
|
"13": {
|
|
"name": "publisher_logo_r",
|
|
"why": "The region twin of entry 10, carrying (R) where 10 carries (TM). Named so it is not mistaken for a second screen the boot path needs. 📌 SOURCE, added 2026-09-01 in the uncited-why backfill: the four bundles are identified in docs/re/ui-title-build-map.md, and the ordinal-versus-entry distinction this entry depends on is docs/re/structures/build-ordinal-vs-entry.md. ⚠️ The sibling references below (\"as entry 10, region twin\") are a citation form too -- they point at another entry in this file rather than at a document, and forcing a path onto them would be mislabelling to satisfy a counter."
|
|
},
|
|
"11": {
|
|
"name": "developer_logos",
|
|
"why": "The GAME ARTS / SETA / studio anima logos -- the developer splash, shown after the publisher wordmark. HANDOFF Q2 and the RE agent's 2026-08-29 render grid; draws 7/7 elements. 📌 SOURCE, added 2026-09-01 in the uncited-why backfill: the four bundles are identified in docs/re/ui-title-build-map.md, and the ordinal-versus-entry distinction this entry depends on is docs/re/structures/build-ordinal-vs-entry.md. ⚠️ The sibling references below (\"as entry 10, region twin\") are a citation form too -- they point at another entry in this file rather than at a document, and forcing a path onto them would be mislabelling to satisfy a counter."
|
|
},
|
|
"14": {
|
|
"name": "developer_logos_r",
|
|
"why": "The region twin of entry 11, as 13 is to 10. 📌 SOURCE, added 2026-09-01 in the uncited-why backfill: the four bundles are identified in docs/re/ui-title-build-map.md, and the ordinal-versus-entry distinction this entry depends on is docs/re/structures/build-ordinal-vs-entry.md. ⚠️ The sibling references below (\"as entry 10, region twin\") are a citation form too -- they point at another entry in this file rather than at a document, and forcing a path onto them would be mislabelling to satisfy a counter."
|
|
}
|
|
}
|
|
},
|
|
"unnamed": {
|
|
"dat/GP_TITLE.pak": "Entries 0/1 and 12/15 are plates never seen running -- not in the boot path, not on any title-side screen, not in the attract loop (HANDOFF Q2). They export under their entry index rather than a name we would be inventing."
|
|
},
|
|
"also_export": {
|
|
"dat/GP_TITLE.pak": {
|
|
"10": {
|
|
"name": "publisher_logo",
|
|
"why": "LOCATED BY ENTRY INDEX, not by a rule. These four bundles declare their sprites directly and have no .rat layout child, so `is_build` cannot see them -- and the RE agent established that NO content rule can: design size fails (every extra composable bundle sampled is 1280x720, the same as every screen) and element count fails (fragments run 2..15 elements in GP_OPTIONS/GP_SAVE_LOAD while these are 3 and 7 -- the ranges overlap). Safe here and not in general: in GP_TITLE the widened set adds exactly these four and all four are real screens, zero fragments. 📌 SOURCE, added 2026-09-01 in the uncited-why backfill: the four bundles are identified in docs/re/ui-title-build-map.md, and the ordinal-versus-entry distinction this entry depends on is docs/re/structures/build-ordinal-vs-entry.md. ⚠️ The sibling references below (\"as entry 10, region twin\") are a citation form too -- they point at another entry in this file rather than at a document, and forcing a path onto them would be mislabelling to satisfy a counter."
|
|
},
|
|
"11": {
|
|
"name": "developer_logos",
|
|
"why": "As entry 10: located by index because no content rule distinguishes a splash from a fragment. 7 elements, all drawn. 📌 SOURCE, added 2026-09-01 in the uncited-why backfill: the four bundles are identified in docs/re/ui-title-build-map.md, and the ordinal-versus-entry distinction this entry depends on is docs/re/structures/build-ordinal-vs-entry.md. ⚠️ The sibling references below (\"as entry 10, region twin\") are a citation form too -- they point at another entry in this file rather than at a document, and forcing a path onto them would be mislabelling to satisfy a counter."
|
|
},
|
|
"13": {
|
|
"name": "publisher_logo_r",
|
|
"why": "As entry 10, region twin. 📌 SOURCE, added 2026-09-01 in the uncited-why backfill: the four bundles are identified in docs/re/ui-title-build-map.md, and the ordinal-versus-entry distinction this entry depends on is docs/re/structures/build-ordinal-vs-entry.md. ⚠️ The sibling references below (\"as entry 10, region twin\") are a citation form too -- they point at another entry in this file rather than at a document, and forcing a path onto them would be mislabelling to satisfy a counter."
|
|
},
|
|
"14": {
|
|
"name": "developer_logos_r",
|
|
"why": "As entry 11, region twin. 📌 SOURCE, added 2026-09-01 in the uncited-why backfill: the four bundles are identified in docs/re/ui-title-build-map.md, and the ordinal-versus-entry distinction this entry depends on is docs/re/structures/build-ordinal-vs-entry.md. ⚠️ The sibling references below (\"as entry 10, region twin\") are a citation form too -- they point at another entry in this file rather than at a document, and forcing a path onto them would be mislabelling to satisfy a counter."
|
|
}
|
|
}
|
|
}
|
|
}
|