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

Bound region service consumer candidates

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-18 12:41:08 -07:00
commit 1ec8749367
2 changed files with 23 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

10
docs/rehost-queue.md
View file

@ -27,7 +27,11 @@ Working rule:
and any stable region-id or class discriminator that can drive shellless city-connection
service. The newly grounded queue-node probe for the atlas-backed kind-`7` notice records is a
negative result on `q.gms`, `p.gms`, and `Autosave.gms`, so the next region pass should not
assume that the transient `[world+0x66a6]` queue family is persisted in ordinary saves.
assume that the transient `[world+0x66a6]` queue family is persisted in ordinary saves; the
region trace now also carries the concrete queued/service owners (`0x00422100`, `0x004337c0`,
`0x00437c00`, `0x004c7520`, `0x004358d0`, `0x00438710`, `0x00420030/0x00420280`,
`0x0047efe0`) so the next pass can focus on the missing saved latches and stable region id/class
rather than on rediscovering the outer service family.
- Reconstruct the save-side placed-structure collection body on top of the newly grounded
`0x36b1/0x36b2/0x36b3` header seam so the blocked city-connection / linked-transit branch can
stop depending on atlas-only placed-structure and local-runtime refresh notes, especially the
@ -91,6 +95,10 @@ Working rule:
consumer candidates rooted at the `Infrastructure` child attach/rebuild/serializer helpers and
the later route/local-runtime follow-on owners. That means the next `0x38a5` pass can be
targeted static mapping instead of another generic scan.
- The region trace now also carries the corresponding atlas-backed candidate owner strip above the
unresolved save latches, so the region frontier is now explicitly “missing persisted owner seam
for `[region+0x25e/+0x276/+0x302/+0x316]` and stable region id/class,” not “unknown service
family.”
- Save inspection now splits the shared `0x5209/0x520a/0x520b` family correctly: the smaller
direct `0x1d5` collection is the live train family and now exposes a live-entry directory rooted
at metadata dword `16`, while the actual region family is the larger non-direct `Marker09`