Deployment Plan — Fixed Deck Timing UI Review
Branch-review mockup for Omega War: Unthinkable, scoped to the Conquest of Helmstedt tactical battle. This review tests whether a Deployment Plan can let the player arrange a fixed 11th Armoured deployment queue before battle without becoming a deck-building screen.
Interview Stage
This page implements the planned `$ui-interview deployment-plan-first` branch review from approved upstream artifacts and the prior implementation plan. The branch id is historical; player-facing language should frame this as a Deployment Plan and fixed deck timing surface.
Final compiled YAML approval was provided on 2026-06-16. The canonical UI branch packet and interview log have been written under `design/unthinkable/`, and the flow-tree decision has been recorded.
UI Assumptions Manifest
| Area | Assumption | Evidence tag |
|---|---|---|
| Product context | Canonical downstream UI design files would belong under `design/unthinkable/`. | [from spec] |
| Parent flow | The reviewed flow is the first playable tactical battle, Conquest of Helmstedt. | [from spec] |
| Selected branch | The UX variation under review is `deployment-plan-first`; player-facing copy should use Deployment Plan / fixed deck timing. | [from artifact] |
| Screen label | The pre-battle surface should be labeled Deployment Plan, not Deck Builder or Loadout. | [from spec] |
| Deck behavior | The scenario deck is fixed; no card editing, roster construction, or quantity controls are present. | [from spec] |
| Deployment planning | The player arranges a planned build order from fixed deck cards and command-post prerequisites. | [from spec] |
| Activation moment | First command-post completion should read as planned availability advancing and Band B arrival. | [from research] |
| Visual assets | Kenney assets are placeholder prototype art and do not set final WW2 art direction. | [from spec] |
Assumptions Gate
Branch Investigation
The UI should prove this corrected thesis: the fixed 11th Armoured deck and command-post prerequisites are readable before battle, without prescribing which strategy the player should use.
| Sibling branch | Boundary to preserve |
|---|---|
| `guided-battle-drill` | Do not stage the first minutes as linear tutorial cards. The Deployment Plan preserves player intent, but the player chooses and acts under pressure. |
| `commanders-tactical-console` | Do not expose every system persistently. Keep deck availability progress focused, not a full data console. |
| `map-first-operational-battle` | Do not make terrain the first mental model. The battlefield takes over after fixed deck identity is understood. |
| `resilient-skirmish-loop` | Do not center save/reload or recovery as the opening promise. Recovery appears after tactical pressure creates the need. |
Branch Verdict Gate
Interactive Mockup
Embedded prototype preview. Use the state buttons to inspect the proposed flow, or open the standalone Deployment Plan mockup. The visual assets are Kenney placeholder art only.
Deployment Plan: Conquest of Helmstedt
11th Armoured Division attacks east against Soviet 2nd Guards Tank Army screens. Win by reaching the conquest target, earning the destruction target, or destroying the enemy command post.
Planned Build Order
Available now.
Available now.
Locked until Motor Pool or Tank Park.
Confirm Deployment Plan
Unit category tabs
Each card has one primary category; transports appear as configuration rows on eligible infantry and towed gun cards.
Band A — Vanguard
Available from Forward Command Post.
Band B — Main Body
Unlocked by Motor Pool / Tank Park, Artillery Battery, Air Liaison, or related Band B surfaces.
Band C — Commitment
Requires Advance Command Post and late support infrastructure.
Plan Panel
Recce, rifles, sappers, light AT.
Follow the plan or open the deployment menu to override.
Unlock Comet Troop and Firefly support.
Motor Pool complete: Band B — Main Body is now live. Comet Troop advances from locked future entry to next planned deployment.
Band B — Main Body Unlocked
Band C remains locked behind Advance Command Post, late support infrastructure, and battlefield control. Centurion Trial Troop stays visible as the planned wonder candidate.
Planned Build Order
Opening deployment.
Second deployment.
Deploy after Motor Pool completes.
Actual Deployment Order
Followed the opening plan.
Adapted to repair the damaged post.
Delayed until 08:10.
Plan verdict: adapted. Fixed 11th Armoured roster remained intact; actual deployment changed when battlefield pressure interrupted the planned queue.
Mockup Gate
Content Requirements
| Page/state | Primary data | User actions | Required states |
|---|---|---|---|
| Deployment Plan | Scenario, fixed deck identity, unit category tabs, band rosters, transport configuration rows, command-post gates, planned build order | Arrange queue, inspect locks, confirm Deployment Plan | Default, reordered queue, locked cards, disabled edit affordances |
| Tactical Entry | Map, capture points, starting units, compact plan panel, next planned deployment, next unlock | Quick-click planned deployment, open normal deployment menu, choose build direction | Normal pressure, quick action available, override menu, locked Band B/C preview |
| Command-Post Unlock | Completed command post, Band B cards, planned availability advancement | Acknowledge unlock, deploy/use next planned Band B card | Unlock success, newly available cards, Band C locked |
| After Action | Planned deployment order, actual deployment order, timing, deviation, verdict | Compare, restart conceptually, review branch verdict | Followed, adapted, delayed, or broken verdict |
Asset Direction
The mockup uses Kenney assets copied from local GeorgeQLe libraries: isometric blocks/building tiles from `assets-2d-isometric` and lock/check/warning/target symbols from `assets-ui-icons`.
Asset Treatment Gate
Proposed Artifacts & File Changes
Confirmed review artifacts:
- `research/unthinkable/_working/preliminary-ui-interview-research.md`
- `alignment/ui-interview-deployment-plan-first.html`
- `alignment/assets/deployment-plan-first/*` placeholder assets and standalone mockup
- `alignment/index.html` entry update
Canonical artifacts written after final compiled YAML approval:
- `design/unthinkable/ui-deployment-plan-first.md`
- `design/unthinkable/ui-deployment-plan-first-interview.md`
- `design/unthinkable/flow-tree-tactical-battle.yaml` UI review and decision update
Artifact Destination & Proposed File Changes Gate
Coverage Checkpoint
Covered
- Product path and parent flow
- Deployment Plan as non-deck-building planning surface
- Tactical entry, command-post unlock, after action
- Sibling branch boundaries
- Kenney placeholder caveat
- Review-only lifecycle
Open For Review
- Approve, retry, or reject branch
- Whether queue controls need stronger planning affordances
- Whether tactical pressure arrives quickly enough
- Whether after-action comparison makes replay intent clear
Coverage Gate
Compile Responses
Answer any gate questions and/or add section feedback, then compile YAML for the agent. Complete approval requires all required gates answered with no unresolved negative feedback.