# Periodic Company Control Lane (2026-04-21) This note preserves the checked evidence behind the current periodic-company queue head, so the short queue can stay focused on the remaining owner question. ## Checked Export - `artifacts/exports/rt3-1.06/compact-event-dispatch-cluster-counts.json` Current checked corpus totals: - `maps_scanned = 41` - `maps_with_dispatch_strip_rows = 38` - `dispatch_strip_record_count = 318` - `dispatch_strip_records_with_trigger_kind = 0` - `add_building_dispatch_record_count = 10` The add-building subset is still only `7` descriptor keys: - `Barracks` - `Bauxite Mine` - `FarmGrain` - `Furniture Factory` - `Logging Camp` - `Port01` - `Warehouse05` ## Concrete Carrier Maps The checked export already keeps the strongest carrier maps visible: - `Texas Tea.gmp` for `548 Add Building Port01` - `Louisiana.gmp` for `563 Add Building Warehouse05` - `Alternate USA.gmp` for the repeated `FarmGrain` / `Logging Camp` `ge34` family - `Chicago to New York.gmp` and `Pacific Coastal.gmp` for the mixed `[-1:4]` cluster The widened full-corpus cluster surface now keeps the strongest non-add-building families visible too: - `dispatch_signature_condition_cluster_occurrence_counts` - `36` for `nondirect-ge1e-h0001-0360-0004-0100-0200-p0000-0000-0000-ffff :: [864:4]` - `27` for `nondirect-ge1e-h0001-ffff-0004-0000-0200-p0000-0000-0000-ffff :: [-1:4]` - `dispatch_signature_condition_cluster_descriptor_keys` - the `36`-occurrence cluster is the broader variable/status family over `Economic Status` plus `Game/Company Variable 1..4` - the `27`-occurrence `[-1:4]` cluster still mixes those variable families with the two checked add-building descriptors `Barracks` and `Bauxite Mine` - `dispatch_signature_condition_cluster_map_paths` - the `36`-occurrence cluster spans `18` maps including `Britain.gmp`, `Chicago to New York.gmp`, `Crossing the Alps.gmp`, and `Eastern China.gmp` - the `27`-occurrence `[-1:4]` cluster spans `14` maps including `Alternate USA.gmp`, `Chicago to New York.gmp`, `Coast to Coast.gmp`, and `Go West!.gmp` - the checked periodic-company trace now mirrors the strongest four of those full-corpus families directly through `near_city_acquisition_nontransport_top_dispatch_signature_condition_clusters`, so the active queue head is no longer backed only by the export file ## Grounded Boundary The active strip is still: - `0x00444d92 -> 0x00432f40(kind 8) -> 0x004323a0 -> 0x00431b20` The checked boundary around that strip is now narrow: - ordinary loaded nondirect rows already reach the `0x00431b20` mutation strip at scale - the export still shows no recovered trigger kind for any of those checked rows - the remaining question is therefore not whether ordinary loaded rows can reach the compact dispatch strip, but where they acquire or bypass the missing trigger-kind control lane before placed-structure mutation opcodes run ## Closest Already-Grounded Retags The checked periodic-company service trace now also exposes these grounded control-lane neighbors directly through: - `near_city_acquisition_nontransport_late_bringup_candidate_branches` - `near_city_acquisition_nontransport_explicit_trigger_kind_retags` The current artifact notes and trace now agree on the same two explicit late retag writers away from ordinary reload: - `SP - GOLD` branch at `0x00443526` - rewrites `[event+0x7ef]` from `1 -> 5` - `Labor` branch at `0x00443601` - rewrites `[event+0x7ef]` from `0 -> 2` So the next non-hook question stays above those already-known title or scenario-specific retags: - which late bringup branch between ordinary reload `0x00433130` and final kind-`8` service `0x00432f40` materializes the live mutation-capable ordinary rows