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

Summarize infrastructure payload envelopes

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-18 14:04:25 -07:00
commit 1011f557e5
2 changed files with 384 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

13
docs/rehost-queue.md
View file

@ -87,6 +87,14 @@ Working rule:
maps the direct `0x38a5` rows into the child count, primary-child ordinal, and per-child payload
callbacks consumed by `0x0048dcf0`, and which restored child fields still retain those embedded
name-pair semantics before route/local-runtime follow-ons take over.
- The save-side `0x38a5` probe is now tighter at the payload-envelope level too: grounded
`q.gms` shows all `138` embedded `0x55f1` rows already live inside complete
`0x55f1 -> 0x55f2 -> 0x55f3` envelopes before the next name row, every embedded `0x55f2` chunk
is the fixed `0x1a` bytes that `0x00455fc0` expects, and the dominant embedded `0x55f3`
payload-to-next-name span is the short `0x06`-byte form across `72` rows. So the next
infrastructure pass should stop asking whether the shared tagged callback sequence is present at
all and instead decode the short `0x55f3` payload role and its relation to the compact-prefix
regimes and primary-child restore path.
- 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
@ -214,6 +222,11 @@ 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 same `0x38a5` probe now also exports payload-envelope summaries directly instead of only flat
name rows: policy/profile tag presence, dominant embedded `0x55f2` and `0x55f3` span lengths,
and sampled row boundaries. That means the next pass can decode the short embedded `0x55f3`
payload lane on top of already grounded row boundaries instead of rediscovering the same
envelopes again.
- That same trace now also ranks those consumers into explicit hypotheses, so the next
infrastructure pass should start with the attach/rebuild strip instead of treating all
candidate owners as equally likely.