User Flow Map - Prototype Build Plan - Tactical Battle
Confirmed 2026-06-16. Product path: unthinkable. Topic: tactical-battle. Rendering tier: prototype.
Confirmed Status
alignment_status: confirmed
Confirmed artifacts: design/unthinkable/prototype-build-plan-tactical-battle.md, design/unthinkable/flow-tree-tactical-battle.yaml, and this alignment page.
This page is current for the completed alignment cycle. Later research or design changes can amend it only by archiving the prior confirmed page and showing what changed.
Table Of Contents
Scope
This page records the approved prototype build-plan synthesis for the first playable tactical battle, Conquest of Helmstedt. The work converts the approved design tree into a concrete ledger for $prototype.
The immediate build target is the approved deployment-plan-first branch. The prototype should show a fixed UK 11th Armoured Deployment Plan, a quick move into tactical pressure, the first command-post unlock, a recovery state, and an after-action planned-vs-actual comparison.
Non-goals remain explicit: no deck builder, no card editing, no card quantities, no alternate roster selection, no campaign-wide deck management, no multiplayer, no production save/load system, no final balance, and no final art direction.
Source Evidence
| Source | Use |
|---|---|
design/unthinkable/flow-tree-tactical-battle.yaml | Parent flow, UX branch states, UI review decision, and manifest build-plan target. |
design/unthinkable/ux-variations-tactical-battle.md | Five UX branches, build-all/UAT intent, sibling branch boundaries, and Deployment Plan First rationale. |
design/unthinkable/ui-deployment-plan-first.md | Approved UI branch packet and concrete prototype surface requirements. |
design/unthinkable/ui-deployment-plan-first-interview.md | Approved UI review gates and final compiled YAML summary. |
research/unthinkable/tactical-vertical-slice-spec.md | Fixed battle contract, faction/deck fixture scope, command-post rules, and prototype exclusions. |
research/unthinkable/game-prototype-test.md | Prototype test questions, playtest flow, observation checklist, and success criteria. |
alignment/ui-interview-deployment-plan-first.html | Confirmed UI alignment page for the approved branch. |
Approved Prototype Build Plan Checkpoint
The checkpoint proposed one build item, no needs-revision branches, four deferred sibling UX branches, and no dropped branches. The user approved it with: "looks good to me".
proto-deployment-plan-first-01None
Four retained UX branches without approved UI packets
None
Build Ledger
| ID | Source user-flow branch | UX variation | UI review | Status | Expected prototype path | Rationale |
|---|---|---|---|---|---|---|
proto-deployment-plan-first-01 | tactical-battle | deployment-plan-first | ui-review-deployment-plan-first-2026-06-16 | built | prototypes/unthinkable/tactical-battle/deployment-plan-first/ | Pre-battle Deployment Plan artifact only: fixed scenario deck, category roster tabs, Band A/B/C availability, deployment queue, build order, and Confirm Deployment Plan. |
proto-tactical-entry-demo-01 | tactical-battle | tactical-entry-demo | ui-review-deployment-plan-first-2026-06-16 | built | prototypes/unthinkable/tactical-battle/tactical-entry-demo/ | Separate in-battle examples demo: Tactical Entry, Motor Pool Complete, and Recovery. |
proto-after-action-demo-01 | tactical-battle | after-action-demo | ui-review-deployment-plan-first-2026-06-16 | built | prototypes/unthinkable/tactical-battle/after-action-demo/ | Separate end-of-game After Action summary after objectives are met. |
Build Sequence
- Build
proto-deployment-plan-first-01as$prototype tactical-battle --variant 1. - Use fixture-backed scenario data, unit cards, bands, command posts, capture points, unlock events, recovery triggers, and after-action sequence.
- Keep the canonical artifact to Deployment Plan -> arrange deployment queue -> Confirm Deployment Plan.
- Keep Tactical Entry, Motor Pool Complete, and Recovery in
tactical-entry-demo/. - Keep After Action in
after-action-demo/. - Keep the prototype small enough to review independently.
$prototype tactical-battle --variant 1Deferred And Dropped Branches
| Branch | Status | Rationale |
|---|---|---|
guided-battle-drill | deferred | Retained UX concept, but no approved UI branch packet exists yet. |
commanders-tactical-console | deferred | Retained UX concept, but no approved UI branch packet exists yet. |
map-first-operational-battle | deferred | Retained UX concept, but no approved UI branch packet exists yet. |
resilient-skirmish-loop | deferred | Retained UX concept, but no approved UI branch packet exists yet. |
| Dropped branches | none | The approved UX variation decision retained all five concepts. |
Interactive Preview
This is a lightweight alignment-page preview of the prototype sequence, not the actual game prototype.
Fixed 11th Armoured deck, queue ordering, category roster tabs, and command-post unlock path.
Map takes over, compact planned-deployment panel remains available, override path stays visible.
Motor Pool or equivalent surface completes; Band B cards arrive as planned deck availability.
Stabilize with Assembly Area, contest with artillery, or rebuild the command chain.
Compare planned deployment order against actual sequence, unlock timing, deviations, and outcome.
Approval Record
| Gate type | Decision | Artifact |
|---|---|---|
| Prototype build item | Approved one pending item: proto-deployment-plan-first-01. | design/unthinkable/prototype-build-plan-tactical-battle.md |
| Deferred branches | Approved deferring planned sibling UX branches until UI packets exist. | design/unthinkable/flow-tree-tactical-battle.yaml |
| Artifact destination | Approved writing the build plan and updating the manifest. | alignment/user-flow-map-tactical-battle.html |
| Post-approval route | Route to $prototype tactical-battle --variant 1. | First pending build item. |