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

Structure linked-transit shellless frontier

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-18 23:14:05 -07:00
commit 0fe2f406ea
2 changed files with 68 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

8
docs/rehost-queue.md
View file

@ -25,9 +25,13 @@ Working rule:
`[company+0x0d3e]` is the shorter peer-cache refresh counter,
`[company+0x0d3a]` is the heavier autoroute site-score refresh counter, and
the route-anchor tuple `[company+0x0d35] / [company+0x7664/+0x7668/+0x766c]` remains save-native
- the train-side follow-ons are bounded too:
`0x00408280 / 0x00408380` are the ranked-site chooser and staged autoroute-entry builder above
the rebuilt site caches, and `0x00409770 / 0x00409830 / 0x00409950` are the append/add/balance
strip above that
- that makes the next linked-transit question narrower:
identify which placed-structure or infrastructure consumer above the timed cache owners
actually turns those rebuilt site caches into roster mutations or route actions
identify which placed-structure or infrastructure owner seam feeds the rebuilt site-cache
lanes consumed by `0x00408280 / 0x00408380`, so the bounded train-side strip can run shelllessly
- Make the next static/rehost slice the near-city industry acquisition owner seam under
`0x004014b0`, not another generic infrastructure pass. The concrete questions are:
- which minimum persisted peer-site fields on the already-grounded `0x006cec20` placed-structure