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

Refresh queue and region companion-set ownership

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-18 17:34:44 -07:00
commit 9d8b4e4031
2 changed files with 36 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

29
docs/rehost-queue.md
View file

@ -35,10 +35,11 @@ Working rule:
- For that top-ranked infrastructure strip, treat the next pass as three exact owner questions
rather than a general “map the consumer” task: whether the `0x38a5` compact-prefix/name-pair
groups feed the first-child triplet clone lane, the caller-supplied payload-stem lane, or only a
later route/local-runtime refresh lane; whether cached primary-child slot `[this+0x248]` is the
first owner-visible bridge from the side-buffer seam into route-entry rebuild; and which child
fields or grouped rows absorb the side-buffer payload before `0x00448a70/0x00493660/0x0048b660`
become relevant.
later route/local-runtime refresh lane; which child fields or grouped rows absorb the
side-buffer payload before `0x00448a70/0x00493660/0x0048b660` become relevant; and, now that the
direct route-entry bridge helpers over `[this+0x206/+0x20a/+0x20e]` are grounded, which later
route/local-runtime owner still carries the remaining mixed exact classes once cached
primary-child slot `[this+0x248]` is demoted to child-list cache/cleanup state.
- Targeted disassembly now tightens that strip further: `0x0048a1e0` clones the first child through
`0x0052e880/0x0052e720`, destroys the prior child, seeds a literal `Infrastructure` child
through `0x00455b70` with payload seed `0x005c87a8`, and republishes the two sampled bands
@ -112,6 +113,20 @@ Working rule:
So the remaining infrastructure question is no longer “what does `0x00490960` build?” or even
“which family is this name row?” but “how do the surviving compact-prefix regimes subdivide
those already-mapped families, especially inside bridge mode `0x01` and track-cap mode `0x0b`?”.
- The direct route-side bridge is grounded now too: `0x0048e140/0x0048e160/0x0048e180` simply
resolve `[this+0x206/+0x20a/+0x20e]` through live route collection `0x006cfca8`, and
`0x0048e1a0` compares those resolved peers against `[this+0x202]`. The neighboring
`0x0048ed30` path is now also narrower: it only tears down child list `[this+0x08]`, clearing
cached primary-child slot `[this+0x248]` when needed, so `[this+0x248]` is no longer the first
route bridge to chase.
- The later route/local-runtime follow-on family is tighter now too: `0x00448a70` is a
world-overlay helper over `[world+0x15e1/+0x162d]`, `0x00493660` is a counter-plus-companion-
region follow-on keyed by `[child+0x218]`, `[child+0x226]`, `[child+0x44]`, and `0x0048dcb0`,
`0x0048b660` is a presentation-color/style owner over `[child+0x216/+0x218/+0x226/+0x44]` and
bit `0x40` in `[child+0x201]`, and `0x0048e2c0/0x0048e330/0x0048e3c0` now read as flag / route-
tracker / region-test helpers rather than hidden payload decoders. So the next infrastructure
slice should stay focused on the remaining mixed exact compact-prefix classes and earlier
child-stream semantics, not on rediscovering the already-bounded presentation owners.
- The new probe correlation now makes that residual even more concrete: on grounded `q.gms`, the
dominant mixed `0x0001/0xff` class splits as `bridge:62 / track_cap:21 / tunnel:19`, while the
pure `0x0002/0xff` class is all bridge and the pure `0x0055/0x00` class is all ballast-cap.
@ -329,6 +344,12 @@ Working rule:
`0x00531150/0x00531030` plus `0x00530720/0x0052e8b0`; they still do not touch
`[region+0x276/+0x302/+0x316]`. That means the remaining region restore target is now the later
owner that rebuilds those latches or the separate tagged body seam that persists them.
- 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
emitter over the world raster, and `0x0044c4b0` is the center-cell bit-`0x10` reseed pass. So
the next region slice should stop revisiting those later owners and stay focused on the still-
missing save-owned latch / severity / stable-id seam.
- The widened real-save region trace rules out one more false lead too: on grounded saves the
`0x55f2` fixed-policy chunk keeps all three reserved dwords at `0x00000000` and the trailing word
at invariant `0x0001`, so that fixed chunk is not currently carrying the missing latch or stable