Tighten remaining atlas edge conclusions

docs/atlas/company-and-ledger.md

@@ -66,7 +66,7 @@ Current bounded compatibility impact:
 
 Highest-value open edge:
 
-- The remaining semantic meaning of the annual finance ladders is now narrower:
+- The remaining semantic meaning of the annual finance policy branches is now narrower:
   stat-family `0x2329/0x1d` is now bounded as current `Book Value Per Share` in the stock-issue
   denominator path, `0x2329/0x0d` is now bounded there as the current cash gate before the
   bond-rate-versus-support ladder, the broader support-adjusted share-price or public-support lane
@@ -79,14 +79,20 @@ Highest-value open edge:
   shareholder-payout lane `0x23`,
   raw slot `0x09` aligns with the Income Statement fuel-cost lane surfaced by tooltip `1309`, and
   derived slot `0x2b` now reads as the rolling net-profits lane. The main remaining gap is the
-  lower policy interpretation of how those lanes are blended inside the annual bankruptcy,
-  dividend, and city-connection ladders. The current strongest read is:
-  bankruptcy = sustained revenue-band-selected cash-and-debt stress plus repeated net-profit
-  failures and fuel burden, with one later deep-distress fallback when cash is below `-300000`
-  and the first three recent profit years all sit at or below `-20000`; stock issuance = a
-  valuation-versus-borrowing screen over
-  support-adjusted price-to-book against the highest live coupon band; dividend adjustment = a
-  weighted recent-profit-per-share target with a small-unassigned-share cash supplement before the
-  board ceiling clamp. The debt-news tail is also now explicit: it compares total retired versus
-  newly issued principal to pick `2882..2886`, and the stock-buyback tail separately publishes
-  `2887` from the accumulated repurchased-share count.
+  exact weight schedule and gate ordering used inside the already-bounded annual bankruptcy,
+  debt, repurchase, stock-issue, and dividend branches. The current strongest read is now:
+  bankruptcy = first the year, toggle, and cooldown gates, then the three-year scan, then the
+  revenue-band-selected cash-and-debt ladder, then the support-adjusted share-price threshold,
+  then the fuel-cost lane and net-profit accumulator; the later deep-distress fallback then
+  re-checks cash below `-300000` plus the first three recent profit years at or below `-20000`.
+  Stock issuance = first the bond/stock toggle gates, then the outstanding-share tranche sizing,
+  then the `55000` proceeds cap, then the support-adjusted price-to-book screen against the
+  highest live coupon band. Dividend adjustment = first the toggle and age gates, then the
+  weighted recent-profit-per-share target, then the small-unassigned-share cash supplement, then
+  the board ceiling clamp. The remaining gap is now mostly the near-cutoff ordering inside the
+  stock-issue lane, and the current strongest read places the liquidity gate at `0x2329/0x0d`
+  before the valuation gate at `0x2329/0x1d`. The dividend-ceiling clamp is already separately
+  bounded on the dividend branch. That is now a final precedence question, not a missing
+  ownership gap in the annual finance verbs themselves. The debt-news tail is also now explicit:
+  it compares total retired versus newly issued principal to pick `2882..2886`, and the
+  stock-buyback tail separately publishes `2887` from the accumulated repurchased-share count.

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

@@ -32,6 +32,9 @@ Current grounded runtime chain:
 - `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:
 
@@ -50,5 +53,12 @@ What this note is for:
 
 Highest-value open edge:
 
-- The deeper gameplay meaning of the per-site local service tables and how those scores drive live
-  city or structure behavior beyond the currently bounded shell summaries.
+- 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.

docs/atlas/multiplayer.md

@@ -150,9 +150,10 @@ Highest-value open edge:
   The negative result is stronger now too: the neighboring replay-band fields
   `[transport+0x176c]`, `[transport+0x1770]`, `[transport+0x1774]`, `[transport+0x177c]`,
   `[transport+0x1780]`, and `[transport+0x1784]` all have direct local lifecycle owners, but
-  `[transport+0x1778]` still only appears as the single read in `0x595bc0`. So the remaining
-  writer is upstream and indirect rather than one ordinary direct field store in the local text
-  cluster. One adjacent staged-route callback is
+  `[transport+0x1778]` still only appears as the single read in `0x595bc0`. So this is no longer
+  a local ownership gap: no local writer is grounded, and the remaining staging path is best read
+  as upstream and indirect rather than one ordinary direct field store in the local text cluster.
+  One adjacent staged-route callback is
   tighter now too: `0x595860` is the submit-result handler below
   `0x5958e0`, using the already-grounded third selector-generation counter at `[transport+0xac0]`
   plus the target at `[transport+0xb48]` to choose whether staged route-callback traffic can

docs/atlas/route-entry-and-trackers.md

@@ -127,8 +127,15 @@ What this note is for:
 
 Highest-value open edge:
 
-- The remaining semantic edge here is narrower now:
-  whether the pre-`1.03` versus `1.03+` tracker metric split has any meaningful downstream effect
-  beyond ranked linked-transit site choice and seeded peer-route choice, since 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 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.

docs/atlas/runtime-and-world-tools.md

@@ -131,5 +131,10 @@ What this note is for:
 
 Highest-value open edge:
 
-- Whether any later gameplay-owned mode bypasses the shell-controller-backed input and frame path
-  for ordinary world interaction.
+- Whether any later gameplay-owned mode introduces a distinct input or frame owner for ordinary
+  world interaction, or whether the grounded `shell_controller_window_message_dispatch` plus
+  `simulation_frame_accumulate_and_step_world` path remains the sole coordinator after world
+  entry and the first grounded non-camera world-input coordinator. Current evidence now points
+  strongly to the second reading: the shell-fed input and frame path remains the only grounded
+  coordinator after world entry, and no separate outer gameplay loop or gameplay-only input object
+  is grounded in the local corpus.