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

Bound tier2 kind-8 setup profile bridge

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

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

@ -93,6 +93,55 @@ One narrower outlier still survives that wider scan:
- `Spanish Mainline.gmp`: same header pair, but `payload_word_0x14 = 1876`,
`payload_byte_0x20 = 0xe3`, `payload_word_0x3b2 = 1`
## Known owner path for the compared fields
The named consumer path for the compared setup-core fields is now bounded too:
- `0x00442400`
`shell_setup_load_selected_profile_bundle_into_payload_record`
materializes the larger setup payload record from the map-style chunk family
- `0x00502220`
`shell_setup_window_publish_selected_profile_labels_and_preview_surface`
then copies the small compared field set through
- `0x0047be50`
`shell_setup_profile_copy_payload_scroll_count_and_campaign_byte_and_seed_row_categories`
That grounded copy path currently lands on staged runtime-profile fields, not on the Tier 2
candidate rebuild strip directly:
- payload `+0x14 -> [profile+0x77]`
- payload `+0x3b2 -> [profile+0x79]`
- payload `+0x3ba -> [profile+0x7b]`
- payload `+0x20 -> [profile+0xc5]`
That setup/profile bridge is not the end of the path, though. The later scenario reset or
reactivation owners already import a subset of those staged values back into the live world before
the coupled Tier 2 rebuild strip runs:
- `0x00436d10`
`scenario_state_reset_defaults_seed_named_availability_collections_and_rebuild_runtime_bridges`
checks `[profile+0xc5]` and, when the setup-not-sandbox branch is active, copies
`[profile+0x77]` into the selected-year world lanes before rerunning
`0x00435603`, `0x00435630`, `0x0041e970`, `0x00412bd0`, `0x00434130`, and `0x00436af0`
- `0x00443a50`
`world_entry_transition_and_runtime_bringup`
mirrors `[profile+0xc5]` into `[world+0x66de]`, restores the selected-year lane from
`[profile+0x77]`, and then re-enters the same rebuild family in the load-side rehydrate band
So the bridge is now narrower and more concrete:
- setup payload `+0x14 -> [profile+0x77] -> selected-year restore -> Tier 2 rebuild family`
- setup payload `+0x20 -> [profile+0xc5] -> campaign/setup gate -> world-entry/reset branch`
- setup payload `+0x3b2/+0x3ba -> [profile+0x79/+0x7b]` are still only grounded on the setup-side
panel and scroll-threshold path, not yet on the later Tier 2 rebuild owners
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
Tier 2 runtime shape through the already-grounded `[profile+0x77/+0xc5]` bridge
- or whether the remaining differentiator still sits elsewhere, most likely in the sparse
recipe/runtime side rather than the setup-panel-only `+0x3b2/+0x3ba` pair
## Current implication
The upstream side of the Tier 2 strip is now bounded more tightly: