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

Add hook debug tooling and refine RT3 atlas

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-08 16:31:33 -07:00
commit 57bf0666e0
38 changed files with 14437 additions and 873 deletions
Download patch file Download diff file Expand all files Collapse all files

28
docs/atlas/route-entry-and-trackers.md
View file

@ -125,17 +125,19 @@ What this note is for:
- Route-style peer-link emission and route-link state
- Track-laying-capacity interactions with route synthesis
Highest-value open edge:
Latest local closure:
- The remaining semantic edge here is now mostly about ranking, not company pressure:
the pre-`1.03` versus `1.03+` tracker metric split still looks meaningful for the weighted
linked-transit site-score cache at `company_rebuild_linked_transit_autoroute_site_score_cache`
`0x00407bd0` and the seeded peer-route chooser at `company_build_linked_transit_autoroute_entry`
`0x00408380`, but current evidence says the company train-pressure target still sums raw site
cache `+0x12` rather than the weighted lanes fed by step count and continuity. The lower
route-entry pair metric still has other grounded consumers such as the initial route sweep and
the train route validator through `0x004a6630`, but no downstream consumer of the cached weighted
site lanes `+0x0e/+0x16` is currently grounded beyond the autoroute selector `0x00408280` and
builder `0x00408380`. So the remaining question here is no longer about current local ownership;
it is only whether some still-ungrounded consumer outside the current corpus also reads those
cached weighted lanes.
- The linked-transit cache split is now locally bounded rather than just suggestive:
the pre-`1.03` versus `1.03+` tracker metric dispatcher still matters for the weighted
autoroute cache lanes at `company_rebuild_linked_transit_autoroute_site_score_cache`
`0x00407bd0`, but the grounded downstream chain now stops at route choice rather than company
pressure. Cache lane `+0x16` feeds the owned-site selector
`company_select_best_owned_linked_transit_site_by_autoroute_score` `0x00408280`, and the
weighted peer-side bands then feed `company_build_linked_transit_autoroute_entry`
`0x00408380`; train-side append and add-train helpers `0x00409770` and `0x00409830` only
inherit that weighted choice by calling the builder. By contrast, the company-wide roster target
at `company_compute_owned_linked_transit_site_score_total` `0x00408f70` still sums only raw
cache `+0x12` before `company_balance_linked_transit_train_roster` `0x00409950` reacts. So this
local semantic edge is effectively closed: the compatibility split perturbs ranked site choice
and seeded autoroute peer choice, not the later train-count target, and any further
weighted-lane consumer would have to live outside the currently grounded local chain.