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

Export world-entry bringup refresh subgraph

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-19 10:30:27 -07:00
commit b2cc64bae4
4 changed files with 3039 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

12
docs/rehost-queue.md
View file

@ -383,6 +383,18 @@ Working rule:
`0x00444d92`, `0x00432f40`, `0x004323a0`, `0x00431b20`, and `0x00433130` at depth `5`,
giving the current ordinary bring-up path a reusable static-analysis surface instead of only
scattered queue prose
- that artifact narrows the immediate owner one step higher too:
the ordinary restore/service pair `0x00433130` and `0x00432f40` now sit directly under
`world_entry_transition_and_runtime_bringup` `0x00443a50` in the checked subgraph, alongside
`0x004133b0` placed-structure refresh, `0x00421510` region refresh, and the
`0x00433bd0/0x00434130/0x004354a0/0x00435603` year-band/state refresh strip. That means the
next static recovery pass can focus on `0x00443a50` ordering and preconditions instead of
treating `0x00444d92` as a floating standalone caller.
- there is now a smaller checked artifact for that owner too:
`artifacts/exports/rt3-1.06/world-entry-bringup-refresh-subgraph.{dot,md}` seeds only
`0x00443a50` at depth `3`, giving a 343-node / 989-edge bringup-refresh surface that is
easier to work from than the broader kind-`8` startup export when the immediate question is
just ordering and neighboring refresh owners.
kinds”; it is the smaller set of scenario-specific records where that sweep explicitly writes
`[event+0x7ef]` itself or a still-later owner does.
- two explicit trigger-kind materializations are now grounded inside that retagger: