jan/rrt
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Demote tier2 kind-8 header class signal

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-19 11:35:37 -07:00
commit b7ca2a4b31
2 changed files with 65 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

19
docs/rehost-queue.md
View file

@ -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: