rrt/docs/atlas/editor-and-site-service.md

Editor and Site Service

Primary atlas sources:

• control-loop-atlas.md#input-saveload-and-simulation
• control-loop-atlas.md#station-detail-overlay

This view isolates the map-editor page families, candidate and site-service runtime chain, and the station-detail or station-list read-side consumers.

Current grounded editor owners:

• map_editor_panel_select_active_section
• map_editor_panel_dispatch_active_section_message
• map_editor_scenario_metadata_panel_refresh_controls
• map_editor_scenario_special_conditions_panel_handle_message
• map_editor_economic_cost_slider_panel_construct
• map_editor_available_chairman_panel_handle_message
• map_editor_city_region_panel_handle_message
• map_editor_territory_panel_handle_message
• map_editor_locomotive_availability_panel_handle_message
• map_editor_industry_availability_panel_handle_message
• map_editor_port_warehouse_cargo_panel_handle_message

Current grounded runtime chain:

• scenario_state_rebuild_port_warehouse_cargo_recipe_runtime_tables
• structure_candidate_collection_rebuild_runtime_records_from_scenario_state
• structure_candidate_rebuild_cargo_membership_and_scaled_rate_tables
• structure_candidate_query_cargo_runtime_summary_channels
• structure_candidate_collection_refresh_cargo_economy_filter_flags
• placed_structure_rebuild_candidate_cargo_service_bitsets
• placed_structure_rebuild_candidate_local_service_tables
• placed_structure_refresh_local_service_score_bundle
• placed_structure_query_candidate_local_service_metrics
• placed_structure_count_candidates_with_local_service_metrics
• placed_structure_query_cached_express_service_class_score

Current grounded shell-side consumers:

• shell_station_detail_format_freight_and_express_summary
• shell_station_detail_format_candidate_local_service_summary
• shell_station_list_format_freight_and_express_availability_summary
• world_render_station_candidate_service_map_overlay

What this note is for:

• Editor page ownership and field semantics
• Port or warehouse cargo recipe runtime path
• Candidate enablement and cargo-economy filtering
• Per-site local service tables and caps
• Station-detail and station-list read-side summaries

Highest-value open 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.