NorthStar

Overview

The operating picture. Scenario-bound.

Indicator

NorthStar defines its own. Insulin uses national supply, days of inventory, projected mortality.

Indicator

Each needs a label, a unit, a direction, and a description saying what it measures.

Indicator

At least one should move before the headline does, or a room has nothing to notice.

Command brief

The mission statement a room reads at the start of each round. Written per scenario, per round.

Situation

What has changed since the last round. Scenario-bound.

Injects and events

Drawn from the scenario's event library. Each carries provenance: precedented, plausible, or a device built for the exercise.

Map

Only if geography matters to NorthStar.

Geography

Injection Point has two map pages because insulin supply is a physical network. If NorthStar's situation is not geographic, this page should not exist and the module should be able to say so.

Intelligence

Platform. Structure carries over unchanged.

Feed

Reference materialFrom the knowledge base

Open dataScenario-specific sources

Submit decision

Platform. The options come from the scenario's levers.

Your cell

CellFrom the module's declared cells

AgencyChosen when joining

Lever options

Each lever declares a label, a delay, and its effects. Insulin has six; NorthStar will have its own.

Logs and reports

Platform. Works unchanged.

Round log

Decisions submitted—

After-action reportGenerated at archive

Research assistant

Platform. Retrieval is scoped by organisation.

Ask

Grounded in the shared doctrine corpus plus anything the organisation has uploaded. Falls back to search when retrieval finds nothing above the relevance floor.

Facilitator

Platform. Works unchanged.

Controls

Advance roundResolves through the scenario's engine

Issue join codeExpires two days out, or later

Inject an eventFrom the scenario library, or written

Participants

Platform. Works unchanged.

Seats

Joined—

Cells occupied—

Audit log

Platform. Works unchanged.

Record

Every state change is a new row rather than an update, so a run replays and the after-action report charts the trajectory rather than the endpoint.