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

Correct acquisition trace owner lanes

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-18 21:04:26 -07:00
commit cf31d0287b
2 changed files with 70 additions and 39 deletions
Download patch file Download diff file Expand all files Collapse all files

26
docs/rehost-queue.md
View file

@ -25,20 +25,24 @@ Working rule:
`0x004014b0`, not another generic infrastructure pass. The concrete questions are:
- which minimum persisted peer-site fields on the already-grounded `0x006cec20` placed-structure
collection feed near-city unowned-industry candidates
- which city/region/company linkage survives save/load strongly enough to drive the proximity
scan
- which placed-structure, city-or-region, and company linkage survives save/load strongly enough
to drive the proximity scan
- whether the acquisition branch can be rehosted as a shellless sibling beside the already
grounded annual-finance helper
- Direct disassembly now narrows that acquisition strip further:
- `0x004014b0` iterates the live class-0 region collection at `0x62b26c`
- `0x004014b0` scans the live placed-structure collection at `0x0062b26c`
- `0x0041f6e0 -> 0x0042b2d0` is the center-cell token gate over the current region
- `0x0047de00 -> 0x0040c990` is the linked-region status branch reused from the city-connection
helper strip
- `0x004801a0` is the route-anchor reachability gate for one candidate site through
`0x00425b90 -> 0x00401860 -> 0x0048e3c0`
- `0x0040d360` filters the region-type lane behind the region vtable `+0x80` byte `0x32`
- `0x0040d540` scores region/company proximity with pending-bonus context
- `0x0040cac0` samples the cached region tri-lane at `[region+0x310/+0x338/+0x360]`
`0x00401860 -> 0x0048e3c0`
- the company-side half of that gate is now explicit too: `0x00401860` validates or rebuilds the
cached linked-transit route-anchor entry id `[company+0x0d35]` from the live route-entry
collection using fallback count lanes `[company+0x7664/+0x7668/+0x766c]`
- `0x0040d360` is the subtype-`4` predicate over the current placed-structure subject's
candidate byte `[candidate+0x32]`
- `0x0040d540` scores site/company proximity with pending-bonus context
- `0x0040cac0` samples the cached site tri-lane at `[site+0x310/+0x338/+0x360]`
- `0x00405920` walks same-company linked site peers above the live placed-structure / peer-site
collection seam
- `0x00420030 / 0x00420280` is the boolean/selector peer-site pair over `0x006cec20`, combining
@ -65,7 +69,13 @@ Working rule:
`[this+0x206/+0x20a/+0x20e]` plus the subordinate payload callback strip, and the
`0x4a9d/0x4a3a/0x4a3b` side-buffer owner only persists route-entry lists, three byte arrays,
five proximity buckets, and the sampled-cell list
- the winning linked company id comes from `[region+0x2a4]`
- the winning site id is staged in `[site+0x2a4]` before `0x004269b0` commits the acquisition
- That leaves the acquisition blocker set tighter than before:
- peer-site and linked-site replay seams are grounded enough for planning
- remaining non-hook gaps are the company cached route-anchor lane
`[company+0x0d35]` plus fallback counts `[company+0x7664/+0x7668/+0x766c]`, and the
placed-structure save/rebuild lanes `[site+0x276]`, `[site+0x2a4]`,
`[site+0x310/+0x338/+0x360]`, and subtype byte `[candidate+0x32] == 4`
- direct disassembly now shows the generic base constructor `0x0052edf0` clearing base state
through `0x0052ecd0` and then writing `[this+0x04]` from caller arg `1`
- `0x00455b70` is the concrete placed-structure specialization constructor feeding