Narrow linked-transit blocker to site-cache inputs

This commit is contained in:
Jan Petykiewicz 2026-04-18 23:16:05 -07:00
commit 879108d7f3
2 changed files with 54 additions and 6 deletions

View file

@ -30,8 +30,9 @@ Working rule:
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 owner seam feeds the rebuilt site-cache
lanes consumed by `0x00408280 / 0x00408380`, so the bounded train-side strip can run shelllessly
identify which placed-structure site-cache input owner seam feeds the rebuilt lanes consumed by
`0x00408280 / 0x00408380`, because the bounded train-side strip
`0x00409770 / 0x00409830 / 0x00409950` is no longer the blocker
- 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