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

Refine next owner questions for blocked seams

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-18 12:56:43 -07:00
commit 4d98967c41
3 changed files with 34 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

13
docs/rehost-queue.md
View file

@ -33,6 +33,13 @@ Working rule:
current best hypothesis as the child attach/rebuild strip
(`0x0048a1e0`, `0x0048dd50`, `0x00490a3c`), with the serializer/load companions next and the
route/local-runtime follow-on family explicitly secondary.
- 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.
- Reconstruct the save-side region record body on top of the newly corrected non-direct tagged
region seam (`0x5209/0x520a/0x520b`, stride hint `0x06`, `Marker09` record stems) now that the
`0x55f3` payload is known to be fully consumed by the embedded profile collection on grounded
@ -56,6 +63,12 @@ Working rule:
(`0x004358d0`) plus the peer/linkage strip (`0x00420030/0x00420280`, `0x0047efe0`), with the
transient producer/queue family explicitly secondary and the queued kind-`7` modal dispatch kept
as shell-adjacent reference only.
- For that top-ranked region strip, treat the next pass as three exact owner questions too: which
persisted owner seam restores or rebuilds `[region+0x25e/+0x276/+0x302/+0x316]`, which stable
region id or class discriminator survives save/load strongly enough to drive `0x004358d0`, and
how far the grounded city-connection peer/linkage helpers
(`0x00420030/0x00420280`, `0x0047efe0`) can be reused directly before the transient queued-notice
family matters again.
- 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