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

Demote tier2 kind-8 setup byte to gate

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-19 11:41:22 -07:00
commit 77986f7e0a
2 changed files with 24 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

16
artifacts/exports/rt3-1.06/runtime-effect-kind8-tier2-setup-core-note.md
View file

@ -149,6 +149,22 @@ The currently grounded Tier 2 relevance of `+0x20` therefore reads more like a b
selected-year/reactivation path inside `0x00436d10 / 0x00443a50`, not like a later direct input to selected-year/reactivation path inside `0x00436d10 / 0x00443a50`, not like a later direct input to
`0x00435630 / 0x00412bd0 / 0x00412c10` through the ordinary `[world+0x66de]` consumer set. `0x00435630 / 0x00412bd0 / 0x00412c10` through the ordinary `[world+0x66de]` consumer set.
That bridge weakens one step further on the profile side:
- `0x00436d10` currently only checks `[profile+0xc5] != 0`
- the validated launch helper `0x004425d0` force-stages `[profile+0xc5] = 1`
- the campaign-side launch branch also forces `[profile+0xc5] = 1`
So the unique raw setup payload byte `+0x20 = 0x3a` in `Louisiana.gmp` is **not** currently a
grounded unique numeric input to the Tier 2 strip. On the current evidence it most likely
collapses to the ordinary nonzero campaign/setup branch before `0x00436d10 / 0x00443a50` run.
That makes the setup-side bridge weaker than it first looked:
- the `+0x20` side is still relevant as a branch gate, but not yet as a unique preserved value
- the `+0x14` selected-year side remains the only currently grounded preserved setup-side scalar on
the bridge
That means the next upstream question is now smaller than before: That means the next upstream question is now smaller than before:
- whether `Louisiana.gmp`'s unique `+0x14/+0x20` setup-core pair is enough to explain its coupled - whether `Louisiana.gmp`'s unique `+0x14/+0x20` setup-core pair is enough to explain its coupled

9
docs/rehost-queue.md
View file

@ -597,7 +597,14 @@ Working rule:
editor metadata checkbox and campaign-gated branches inside `0x00442c30`, not the core editor metadata checkbox and campaign-gated branches inside `0x00442c30`, not the core
Tier 2 helpers directly. So the likely Tier 2 relevance of `+0x20` is the branch gate inside Tier 2 helpers directly. So the likely Tier 2 relevance of `+0x20` is the branch gate inside
`0x00436d10 / 0x00443a50` before the rebuild family runs, not a later direct `0x00436d10 / 0x00443a50` before the rebuild family runs, not a later direct
`[world+0x66de] -> 0x00435630/0x00412bd0/0x00412c10` data path. `[world+0x66de] -> 0x00435630/0x00412bd0/0x00412c10` data path. The same note now weakens that
bridge a step further: current grounded profile-side consumers treat `[profile+0xc5]` as a
nonzero gate, and both `0x004425d0` and the campaign-side launch branch force it to `1`.
So the raw `Louisiana.gmp` setup payload byte `+0x20 = 0x3a` is not yet a grounded unique
numeric Tier 2 input; on the current evidence it collapses to the ordinary nonzero campaign or
setup branch before `0x00436d10 / 0x00443a50` run. That shifts even more weight back onto the
sparse recipe/runtime family, with `+0x14` the only currently grounded preserved setup-side
scalar still crossing the bridge.
kinds”; it is the smaller set of scenario-specific records where that sweep explicitly writes kinds”; it is the smaller set of scenario-specific records where that sweep explicitly writes
`[event+0x7ef]` itself or a still-later owner does. `[event+0x7ef]` itself or a still-later owner does.
- two explicit trigger-kind materializations are now grounded inside that retagger: - two explicit trigger-kind materializations are now grounded inside that retagger: