Preserve periodic company control lane evidence

docs/rehost-queue.md

@@ -12,6 +12,7 @@ This file is the short active queue for the current runtime and reverse-engineer
 
 - Keep the periodic-company trace as the main shellless simulation frontier, with the next concrete control-lane pass focused on the ordinary loaded runtime-effect strip `0x00444d92 -> 0x00432f40(kind 8) -> 0x004323a0 -> 0x00431b20`.
   The checked `rt3_105/maps` compact-dispatch corpus is now exported directly: `41` maps scanned, `38` with dispatch-strip rows, `318` nondirect rows total, and the add-building subset is only `10` grouped occurrences across `7` descriptor keys, all still missing trigger kind. The active open question is therefore which ordinary loaded rows acquire or bypass the missing trigger-kind control lane before they can reach placed-structure mutation opcodes.
+  Preserved checked control-lane detail now lives in [Periodic company control lane](rehost-queue/periodic-company-control-lane-2026-04-21.md).
 - Keep the next static Tier-2 building pass focused on the earlier seed/projection seam into `0x00412d70`, not another broad `BuildingTypes` sweep.
   The grounded owner strip is `0x004196c0 -> 0x00414490 -> 0x00416ce0 -> 0x00419230`, but the active open question is which earlier seed/projection path lets the fixed candidate-table cluster at rows `35/43/45..66` reach `0x00412d70` with nonzero `[candidate+0xba/+0xbb]` before `0x00419230` clones or renames it.
   Preserved checked row-family detail now lives in [Tier2 candidate row families](rehost-queue/tier2-candidate-row-families-2026-04-21.md).
@@ -19,5 +20,6 @@ This file is the short active queue for the current runtime and reverse-engineer
 ## Preserved Detail
 
 - [Archive snapshot](rehost-queue/archive-2026-04-19.md)
+- [Periodic company control lane](rehost-queue/periodic-company-control-lane-2026-04-21.md)
 - [Tier2 candidate row families](rehost-queue/tier2-candidate-row-families-2026-04-21.md)
 - [Progress history](history/progress-history.md)

docs/rehost-queue/README.md

@@ -4,5 +4,7 @@ This directory preserves older queue snapshots and long-form implementation note
 useful as evidence, but should not stay in the short active queue file.
 
 - `archive-2026-04-19.md`: preserved detailed queue snapshot from the pre-index cleanup.
+- `periodic-company-control-lane-2026-04-21.md`: checked compact-dispatch/control-lane evidence
+  for the active periodic-company queue head.
 - `tier2-candidate-row-families-2026-04-21.md`: checked candidate-table row-family split for the
   active Tier-2 `0x00412d70` queue head.

docs/rehost-queue/periodic-company-control-lane-2026-04-21.md

@@ -0,0 +1,63 @@
+# 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
+
+## 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 current artifact notes already bound 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