Mission Orders Board
Situation, Mission, Battle Conditions, Battlefield, Escalation, and Readiness in one scrollable field order.
Open screenOmega War · Unthinkable · Alignment date 2026-07-10
Battle Briefing screen build
Three fixture-backed briefing structures are built for direct comparison before any winner is selected or inserted into the tactical-battle flow.
Alignment status: confirmed
Confirmed artifact paths: `design/unthinkable/ux-variations-battle-briefing.md`, `design/unthinkable/ui-battle-briefing.md`, and `prototypes/unthinkable/tactical-battle/battle-briefing/`.
Approval source: the user-provided Battle Briefing Variation Prototype plan explicitly authorized building all three variants before selection. This finished comparison cycle remains amendable, but no production UI is approved.
First-value journey
Entry: briefing comparison hub. First value: the player can name the mode, forces, mission, and battle-ending conditions. Primary path: open one briefing, understand the battle, continue to the existing Deployment Plan. Exit: `deployment-plan-first/index.html`.
The briefing establishes context. The existing planner establishes fixed-deck timing. Neither surface tells the player which strategy to use.
Built variants
Helmstedt Command Map
Code-native SVG schematic with inspectable objectives, terrain, command yards, and optional Checkpoint Alpha.
Open screenSignal Room Briefing
Five manual frames with persistent Skip, progress, Back/Next, and always-available Mission Essentials.
Open screenShared fixture
| Field | Shared fact |
|---|---|
| Scenario / mode | Conquest of Helmstedt · Conquest only |
| Forces | UK/Commonwealth 11th Armoured Division versus Soviet 2nd Guards Tank Army |
| Objectives | Five; four value-1 resources and value-3 CP-C command point |
| Escalation | Phase A Vanguard, Phase B Main Body, Phase C Commitment |
| Map event | Checkpoint Alpha grants temporary local pressure only |
| Exit | Existing Deployment Plan |
Ordered element-batch ledger
| Variant | Flow step | Elements added | Status |
|---|---|---|---|
| Mission Orders | Situation and mission | Masthead, mode, forces, mission | wired |
| Mission Orders | Battle contract | Victory, defeat, objectives, Checkpoint boundary | wired |
| Mission Orders | Escalation and readiness | Phases, readiness, planner handoff | wired |
| Command Map | Spatial battlefield | SVG terrain, five objectives, landmarks, Checkpoint | wired |
| Command Map | Accessible inspection | Keyboard markers, intel panel, equivalent list | wired |
| Command Map | Mission exit | Legend, essentials, planner handoff | wired |
| Signal Room | Guided sequence | Five frames, progress, Back/Next | wired |
| Signal Room | User control | Skip, variation exit, native keyboard controls | wired |
| Signal Room | Essential facts | Persistent Mission Essentials, final planner CTA | wired |
Serial visual checkpoints
Mission Orders: the first viewport establishes forces, mission, and battle conditions; lower sections continue without interaction friction.
Command Map: the five-point shape and central value read immediately; pointer selection updates the intelligence panel and equivalent list with a double-ring selected state.
Signal Room: all five frames were walked in order; Back restored the prior frame; Skip and Mission Essentials remained available.
Exact-viewport screenshot evidence is written under `prototypes/unthinkable/tactical-battle/battle-briefing/evidence/` by the browser-smoke gate.
Fake-data boundary
All state comes from the plain-script `window.BATTLE_BRIEFING_DATA` fixture. No fetch, module, CDN, database, storage, planner state transfer, analytics, or runtime dependency is present. The output is disposable comparison evidence, not production code.
Deferred infrastructure and decisions
- Winner selection and consolidation
- Insertion ahead of Deployment Plan
- Generated imagery, video, voiceover, audio, and autoplay
- Analytics, persistence, and runtime state transfer
- Alternate battle modes, campaign context, deck editing, or detailed ability documentation
Read-only approval record
Decision: build all three before choosing a winner. Scope: approved for comparison only. Production selection: pending for BB-01, BB-02, and BB-03. Next gate: manual variant evaluation in `tasks/manual-todo.md`.