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

Narrow region handoff to post-load owner strip

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-18 20:54:15 -07:00
commit a9b6b2c809
2 changed files with 88 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

19
docs/rehost-queue.md
View file

@ -630,6 +630,25 @@ Working rule:
should now bias even more toward the later region-local rebuild beneath the `0x00444887`
continuation, while still keeping `0x0040b5d0` as a weaker adjacent prerequisite rather than
treating it as the primary hidden owner.
- The next owner family is narrower now too: the checked-in shell-load subgraph and function map
place `world_load_saved_runtime_state_bundle` `0x00446d40` directly ahead of the post-load
generation pipeline `0x004384d0`, which is now the first explicit non-hook owner family above
the ruled-down `0x00444887` continuation. The current grounded stage order is concrete enough to
split the next static pass: `319` refreshes route entries, auxiliary route trackers, and then the
placed-structure replay strip `0x004133b0`; `320` runs the region-owned building setup strip
`0x00421c20 -> 0x004235c0`; and `321` runs the economy-seeding burst `0x00437b20` plus the
cached region summary refresher `0x00423d30`. That means the next region closure pass should
chase this `0x004384d0` handoff family directly instead of treating the remaining
`[region+0x2a4]` / `[region+0x310/+0x338/+0x360]` gap as a generic continuation below
`0x00444887`.
- The `319` lane is the strongest bridge inside that family: `0x004133b0` drains queued
placed-structure ids through `0x0040e450`, sweeps every live site through `0x0040ee10`, and then
reaches the already-grounded linked-site follow-on `0x00480710`. The `320` and `321` lanes are
still explicit but weaker: `0x00421c20 -> 0x004235c0` stays on region-side demand balancing and
structure placement, while `0x00437b20 -> 0x00423d30` only refreshes the cached category band
`[region+0x27a/+0x27e/+0x282/+0x286]`. So the next non-hook region work should start from the
post-load `319` placed-structure replay seam and only then revisit the narrower region-side
`320/321` branches if the exact field bridge is still missing.
- The later restore-side region owners are narrowed further now too: the `0x00421ce0 ->
0x0041fb00 -> 0x00421730` sweep is class-`0` raster/id rebuild, `0x004881b0` is a companion
region-set cell-count rebuild over `[region+0x3d/+0x41]`, `0x00487de0` is a border-segment