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

Tier kind-8 late rebuild candidates

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-19 10:56:48 -07:00
commit 6ecee630a7
4 changed files with 727 additions and 31 deletions
Download patch file Download diff file Expand all files Collapse all files

12
docs/rehost-queue.md
View file

@ -470,7 +470,17 @@ Working rule:
`artifacts/exports/rt3-1.06/runtime-effect-kind8-post-reload-candidates.md` extracts the
currently plausible late `0x00443a50` branches between ordinary reload and final kind-`8`
service, with the current bias explicitly shifted away from the known title-fixup branch and
toward non-title-specific late bringup owners.
toward the Tier 2 candidate/world-state rebuild owners rather than the Tier 3
shell-progress/year-scalar refresh strip.
- the Tier 2 owner strip is checked in separately now too:
`artifacts/exports/rt3-1.06/runtime-effect-kind8-tier2-candidate-rebuild-subgraph.md`
shows the current bounded rebuild band rooted at `0x00412c10 / 0x00412bd0 / 0x00437737`
reaching candidate runtime-record rebuild `0x00412d70 / 0x00412fb0`,
named-availability query/upsert `0x00434ea0 / 0x00434f20`,
cargo-economy filter refresh `0x0041eac0`,
port/warehouse recipe rebuild `0x00435630`,
and only then the later world bringup / event-service neighborhood
`0x004384d0 / 0x00443a50 / 0x00432f40`.
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: