From b7ca2a4b312379ae58530ba529c23dd20f7d9562 Mon Sep 17 00:00:00 2001 From: Jan Petykiewicz Date: Sun, 19 Apr 2026 11:35:37 -0700 Subject: [PATCH] Demote tier2 kind-8 header class signal --- ...time-effect-kind8-tier2-setup-core-note.md | 56 +++++++++++++++++-- docs/rehost-queue.md | 19 +++++-- 2 files changed, 65 insertions(+), 10 deletions(-) diff --git a/artifacts/exports/rt3-1.06/runtime-effect-kind8-tier2-setup-core-note.md b/artifacts/exports/rt3-1.06/runtime-effect-kind8-tier2-setup-core-note.md index b3663e2..de4e856 100644 --- a/artifacts/exports/rt3-1.06/runtime-effect-kind8-tier2-setup-core-note.md +++ b/artifacts/exports/rt3-1.06/runtime-effect-kind8-tier2-setup-core-note.md @@ -50,18 +50,64 @@ So `Louisiana.gmp` is currently unique among the shipped carrier set on the cand sentinel pair, while `Alternate USA.gmp` stays separately unique on the recognized `rt3-105-map-container-v1` header pair. +## Wider map-corpus check + +A wider `compare-setup-payload-core` pass over all 41 bundled `rt3_105/maps/*.gmp` files changes +the candidate-header read materially: + +- `(0x00000000, 0x00000000)` appears on 31 maps +- `(0xcdcdcdcd, 0xcdcdcdcd)` appears on 9 maps +- `(0x10000000, 0x00009000)` appears only on `Alternate USA.gmp` + +Current `0xcdcdcdcd / 0xcdcdcdcd` maps in that wider corpus: + +- `Argentina Opens Up.gmp` +- `Britain.gmp` +- `Crossing the Alps.gmp` +- `Greenland Growing.gmp` +- `Japan Trembles.gmp` +- `Louisiana.gmp` +- `Pacific NW.gmp` +- `South East Australia.gmp` +- `Spanish Mainline.gmp` + +So the candidate-header sentinel pair is no longer a plausible `Louisiana`-specific upstream +explanation by itself. + +That wider read also matches the already checked atlas note in +`post-load-generation-paintterrain-and-save-load-restore.md`: the candidate-availability table +header scan had already narrowed the visible family to those same three stable +`(header_word_0, header_word_1)` pairs, with the `0xcdcdcdcd` class behaving like reused +source-family framing rather than a direct availability payload or a unique scenario-side trigger. + +One narrower outlier still survives that wider scan: + +- no other bundled `rt3_105` map matches the full current `Louisiana.gmp` setup-core tuple + `payload_word_0x14 = 1870`, `payload_byte_0x20 = 0x3a`, `payload_word_0x3b2 = 2`, + `candidate_header = 0xcdcdcdcd / 0xcdcdcdcd` +- even the nearest header-class peers still diverge: + - `Argentina Opens Up.gmp`: same header pair, but `payload_word_0x14 = 1880`, + `payload_byte_0x20 = 0x57`, `payload_word_0x3b2 = 1` + - `Crossing the Alps.gmp`: same header pair, but `payload_word_0x14 = 1875`, + `payload_byte_0x20 = 0x8f`, `payload_word_0x3b2 = 1` + - `Spanish Mainline.gmp`: same header pair, but `payload_word_0x14 = 1876`, + `payload_byte_0x20 = 0xe3`, `payload_word_0x3b2 = 1` + ## Current implication The upstream side of the Tier 2 strip is now bounded more tightly: - the current `Louisiana.gmp` recipe/runtime outlier status is not explained by `payload_word_0x3b2` alone, because `Chicago to New York.gmp` also carries `2` -- but `Louisiana.gmp` does stand out on the candidate-header sentinel pair +- and `Louisiana.gmp` no longer stands out on the candidate-header sentinel pair once the broader + 41-map corpus is included +- but `Louisiana.gmp` still keeps a unique combined setup-core tuple once the broader corpus is + included So the next Tier 2 upstream question is narrower: -- whether the unique `0xcdcdcdcd / 0xcdcdcdcd` candidate-header state in `Louisiana.gmp` is - relevant to the coupled +- whether `Louisiana.gmp`'s remaining upstream setup-core outlier is a more specific combination of + `payload_word_0x14`, `payload_byte_0x20`, and the sparse recipe/runtime profile, rather than the + coarse candidate-header class itself, in the coupled `0x00435630 / 0x00412d70 / 0x00412fb0 / 0x00412c10` - rebuild strip, or whether it is only another container-side artifact unrelated to the shipped - `Add Building Warehouse05` row. + rebuild strip. diff --git a/docs/rehost-queue.md b/docs/rehost-queue.md index 9837f89..7a10658 100644 --- a/docs/rehost-queue.md +++ b/docs/rehost-queue.md @@ -552,11 +552,20 @@ Working rule: `artifacts/exports/rt3-1.06/runtime-effect-kind8-tier2-setup-core-note.md` widens that upstream comparison across all six bundled add-building carriers. It shows `Louisiana.gmp` is not unique on `payload_word_0x3b2` (`Chicago to New York.gmp` also has `2`) - but is unique among the shipped carrier set on the candidate-header sentinel pair - `0xcdcdcdcd / 0xcdcdcdcd`, while `Alternate USA.gmp` stays separately unique on the - recognized `rt3-105-map-container-v1` header pair. That narrows the next upstream Tier 2 - question to whether the `Louisiana` candidate-header state actually matters to the coupled - rebuild strip or is just another container-side artifact. + and shows `Louisiana.gmp` is unique among that six-map carrier subset on the candidate-header + sentinel pair `0xcdcdcdcd / 0xcdcdcdcd`, while `Alternate USA.gmp` stays separately unique on + the recognized `rt3-105-map-container-v1` header pair. The same note now widens further across + all 41 bundled `rt3_105` maps and shows the candidate-header pair is not actually + `Louisiana`-specific in the full corpus at all: nine maps share `0xcdcdcdcd / 0xcdcdcdcd`, + matching the older atlas read that this looks like coarse scenario-family framing instead of a + direct Tier 2 trigger. That trims the next upstream Tier 2 question again: focus on the more + specific remaining setup-core combination (`payload_word_0x14`, `payload_byte_0x20`, plus the + sparse recipe/runtime profile), not on the candidate-header class by itself. The same widened + note now records that the full current `Louisiana.gmp` tuple + (`payload_word_0x14 = 1870`, `payload_byte_0x20 = 0x3a`, `payload_word_0x3b2 = 2`, + `candidate_header = 0xcdcdcdcd / 0xcdcdcdcd`) is still unique across the 41-map corpus even + after the coarse header class is demoted, so the next pass should compare that tighter tuple to + the sparse recipe/runtime family rather than reopening the broad header-pair question. kinds”; it is the smaller set of scenario-specific records where that sweep explicitly writes `[event+0x7ef]` itself or a still-later owner does. - two explicit trigger-kind materializations are now grounded inside that retagger: