Ground linked-transit cache cadence trace inputs
This commit is contained in:
parent
edd36aa607
commit
efa3b6a2a7
2 changed files with 99 additions and 19 deletions
|
|
@ -20,7 +20,14 @@ Working rule:
|
|||
`0x004019e0 -> 0x00406050` plus peer helpers
|
||||
`0x00420030 / 0x00420280 / 0x0047efe0`
|
||||
- `linked_transit_roster_maintenance` carries
|
||||
`0x004019e0 -> 0x00409950`
|
||||
`0x004019e0 -> 0x00409720 -> 0x004093d0 / 0x00407bd0 -> 0x00408f70 -> 0x00409950`
|
||||
- the linked-transit timing seam is now grounded save-side too:
|
||||
`[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
|
||||
- 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
|
||||
- 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
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue