Support sector-specific Truthtrance movement

docs/CURRENT_STATUS.md

@@ -20,6 +20,14 @@ open mode gates.
 Keep identified Basic-function gaps ahead of Advanced and wider interactions.
 Prototype labels and final acceptance gates remain.
 
+**Truthtrance ground-movement sectors — 27 October. Prototyped / Partial.**
+A future physical-movement condition can name the whole destination territory
+or one exact printed sector. Separate eligible moves may satisfy separate
+clauses; each minimum counts one actual group. Older territory-only progress
+never invents a sector. Native guidance and minimal legal bots use actual
+movement choices; broader combinations and deployed acceptance remain open.
+[Scope](TRUTHTRANCE_MOVEMENT_PROMISES.md#ground-movement-destination-sector--27-october-2026).
+
 **Truthtrance shipment sectors — 27 October. Prototyped / Partial.**
 A future reserve-shipment condition may name an exact printed sector or the
 whole territory. Sector and territory clauses share the original physical

docs/IMPLEMENTATION_STATUS.md

@@ -1,5 +1,14 @@
 # Dune implementation status
 
+## 27 October 2026 — Truthtrance ground-movement sector
+
+Future physical-movement conditions may name an exact printed sector.
+Standalone, mixed, expression, travel and whole-turn controls share the native
+move, per-group progress and legal guidance. Separate moves can satisfy
+different clauses; legacy territory maxima never imply a sector. Broader
+combinations, complete rules and deployed acceptance remain open.
+[Contract](TRUTHTRANCE_MOVEMENT_PROMISES.md#ground-movement-destination-sector--27-october-2026).
+
 ## 27 October 2026 — Truthtrance reserve shipment sector
 
 An optional exact printed sector is part of the existing future reserve

docs/RULE_DECISIONS.md

@@ -1,5 +1,14 @@
 # Rule decision index
 
+## Truthtrance and ground-movement sector — 27 October 2026
+
+A sector-qualified current-turn question counts a real physical ground group
+ending in that printed sector. Separate eligible moves can satisfy separate
+clauses; smaller groups are never added together. This is a provisional online
+application of the FAQ's current-turn question permission, not a separate
+publisher timing ruling.
+[Contract](TRUTHTRANCE_MOVEMENT_PROMISES.md#ground-movement-destination-sector--27-october-2026).
+
 ## Truthtrance and reserve shipment sector — 27 October 2026
 
 An optional exact sector names the same original reserve-shipment event as

docs/TRUTHTRANCE_MOVEMENT_PROMISES.md

@@ -688,3 +688,25 @@ Framework aliases/CSS stubbing make this server-rendered evidence, not browser,
 visual or deployed acceptance. Full modes, wider preparations/timing/modules,
 comprehensive assurance and deployed acceptance remain open. No saved-room/D1
 operation, reset, restart or deployment.
+
+## Ground-movement destination sector — 27 October 2026
+
+**Prototyped / Partial.** The publisher FAQ (November 2020, p. 8) permits
+current-turn Yes/No questions; naming the destination sector is a provisional
+application of the project's online binding procedure. A movement clause may
+name any sector of a printed territory or a single printed sector and requires
+one actual physical ground-moving group of the selected minimum. Shipment,
+marker-only movement and special relocations retain their existing distinctions.
+
+Standalone, expression, mixed, travel and whole-turn questions use the same
+native legal movement and shared private guide. No forbids the matching move;
+Yes retains an available native completion. Different actual moves can satisfy
+different positive sector clauses when movement allowances and cards permit.
+Per-sector maxima record each qualifying group without adding smaller moves;
+old territory-wide progress is preserved and never implies an unrecorded sector.
+Dynamic board locations remain native legal destinations but cannot be named
+as printed-sector claims in this prototype.
+
+Runtime cases use a genuine Basic setup and actual physical shipment, Hajr and
+movement actions; complete expansion interactions, broader source review,
+browser and deployed acceptance remain open.