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/editor-and-site-service.md
View file

@ -34,7 +34,10 @@ Current grounded runtime chain:
- `placed_structure_refresh_local_service_score_bundle`
- `placed_structure_query_candidate_local_service_metrics`
- `placed_structure_count_candidates_with_local_service_metrics`
- `placed_structure_get_nth_candidate_id_with_local_service_metrics`
- `placed_structure_query_cached_express_service_class_score`
- `placed_structure_refresh_candidate_local_service_comparison_cache_against_peer_site`
- `placed_structure_select_best_candidate_id_by_local_service_score`
Current grounded shell-side consumers:
@ -51,14 +54,19 @@ What this note is for:
- Per-site local service tables and caps
- Station-detail and station-list read-side summaries
Highest-value open edge:
Resolved edge:
- The deeper gameplay meaning of the per-site local service tables is now mostly about whether
those scores stay confined to placement, overlay, and station-summary presentation through the
query helpers, or whether the same query outputs also feed live cargo-economy filter flags,
per-site service-cap rebuilds, or nearby-structure behavior beyond the currently bounded shell
summaries. The grounded chain strongly suggests the read-side path is dominant, the query
helpers themselves still read as read-only consumers, and the only grounded mutation bridge is
the collection-wide cargo-economy filter refresh. The remaining open question is whether that
filter refresh is the full policy sink for the local service tables or whether an additional
mutation-side writer exists outside the local corpus.
- The per-site local service query family is now bounded as predominantly read-side. Above the
mutation and rebuild lane, the grounded helpers are:
`placed_structure_query_candidate_local_service_metrics`,
`placed_structure_count_candidates_with_local_service_metrics`,
`placed_structure_get_nth_candidate_id_with_local_service_metrics`,
`placed_structure_query_cached_express_service_class_score`,
`placed_structure_refresh_candidate_local_service_comparison_cache_against_peer_site`, and
`placed_structure_select_best_candidate_id_by_local_service_score`.
- Their grounded callers are shell summaries, shell detail rows and popups, the world preview
overlay, one company-side autoroute score cache rebuild, and one peer-site comparison cache.
None of the newly closed callers acts as a policy writer back into candidate or site state.
- The only grounded mutation bridge on this edge remains
`structure_candidate_collection_refresh_cargo_economy_filter_flags`, which writes the derived
enabled or filtered state into `[entry+0x56]` before rebuilding the visible counts.