Bias region handoff away from support counters

This commit is contained in:
Jan Petykiewicz 2026-04-18 20:39:38 -07:00
commit ea8ee9d753
2 changed files with 9 additions and 1 deletions

View file

@ -621,6 +621,13 @@ Working rule:
load/save callbacks `0x00487670/0x00487680`, so the next pass should bias more heavily toward
support refresh `0x0040b5d0` or the later region-local rebuild than toward territory payload as
the hidden source of `[region+0x2a4]` and `[region+0x310/+0x338/+0x360]`.
- The support side is less opaque now too: the same atlas already bounds `0x0040b5d0` above
support collection `0x0062b244`, whose grounded live owners maintain goose-entry counters,
neighboring world support lanes `[world+0x4c9a/+0x4c9e/+0x4ca6/+0x4caa]`, and selected
support-entry state rather than an obvious per-region acquisition latch family. So the next pass
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 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