Bound add-building back half to latent map coverage
This commit is contained in:
parent
7a26063656
commit
9f1ee6550e
1 changed files with 6 additions and 0 deletions
|
|
@ -371,6 +371,12 @@ Working rule:
|
||||||
alternate live owner for descriptor-side add-building candidate ids; current non-hook evidence
|
alternate live owner for descriptor-side add-building candidate ids; current non-hook evidence
|
||||||
still routes stem resolution back through the live candidate collection that tops out at the
|
still routes stem resolution back through the live candidate collection that tops out at the
|
||||||
contiguous named run `0..66`
|
contiguous named run `0..66`
|
||||||
|
- the shipped-map compact-dispatch corpus is narrower than the descriptor strip too:
|
||||||
|
`runtime inspect-compact-event-dispatch-cluster-counts rt3_wineprefix/drive_c/rt3_105/maps`
|
||||||
|
scans all `41` bundled maps and finds add-building dispatch occurrences only for descriptors
|
||||||
|
`506`, `507`, `521`, `526`, `528`, `548`, and `563`. No bundled-map dispatch rows currently
|
||||||
|
exercise descriptor ids `570..613`, so the back half of the widened add-building strip is now
|
||||||
|
bounded as descriptor-grounded but latent in the shipped compact-event corpus
|
||||||
- the concrete owner strip above that bundle is grounded now too:
|
- the concrete owner strip above that bundle is grounded now too:
|
||||||
`0x00433060` is the direct non-direct serializer loop that writes `0x4e99/0x4e9a/0x4e9b`,
|
`0x00433060` is the direct non-direct serializer loop that writes `0x4e99/0x4e9a/0x4e9b`,
|
||||||
calls `0x00430d70` per live collection row, and sits beside the sibling `0x00433130` size/load
|
calls `0x00430d70` per live collection row, and sits beside the sibling `0x00433130` size/load
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue