Project Roadmap

MissionChief UK is maintained as an evidence-led operational information system rather than a one-off collection of articles.

Programme status

Stages 1–42 are delivered.

Release: v1.4.0
API contract: v1
Official UK missions: 1,062
Canonical mission records: 1,079
Fully canonical official records: 1,062 / 1,062
Deployable-resource records: 104
Infrastructure records: 20
Training and role records: 12
Observed vehicle type IDs mapped: 73 / 73
Vehicle field decisions resolved: 936 / 936
Service operational programmes: complete
Cross-service strategy: complete
Alliance Operations: complete
Account Readiness Planner: complete
UX and accessibility audit: complete

Delivered foundation — Stages 1–12

project identity and information architecture
player journey and service-guide framework
vehicle, mission, building, personnel and training models
planning-tool architecture
evidence and verification standards
contribution controls and templates
Draft 2020-12 schemas and recursive validation
GitHub Pages delivery through Actions

Delivered operational data — Stages 13–27

Delivered data and tool platform — Stages 28–36

Delivered operational-guide programme — Stage 37A–37I

Fire and Rescue progression, specialist systems, training, airfield/railway, severe weather, major incidents and live mission-family pressure
Ambulance and HART patient throughput, specialist response, command, mass casualty, welfare and HEMS
Police and Public Safety patrol, custody, armed, roads, dog, mounted, public order, air support and railway dependencies
Coastguard and Lifeboat shore, vessel, air, trailer, towing, mud, rope and flood rescue
Mountain Rescue and Search and Rescue HQ off-road, search, command, drone, dog and personnel systems
Bomb Disposal and EOD land, heavy, marine and railway ordnance response
Airfield Operations ARFF, command, operations, foam, water, HazMat, access and casualty tiers
Recovery and HGV Recovery outcome semantics, overlays, regional capacity and recovery-to-readiness
Railway Police and Railway Fire corridor, hub, tunnel, command and major-incident resilience

Delivered strategy and operations — Stages 38–41

Stage 38 — Cross-Service Account Progression

universal expansion gates and readiness states
foundation through mature regional account models
cross-service dependency and handoff matrix
route-, destination-, access-, cluster-, hub- and relief-base station placement
urban, rural, coastal and alliance-supported assumptions

Stage 39 — Alliance Operations

member, dispatcher and administrator modes
onboarding, permissions and least privilege
contribution-policy and shared-infrastructure models
mutual support, donor reserve, events and major incidents
recruitment, inactivity, moderation and external-tool boundaries

Stage 40 — Account Readiness Planning Suite

local-only mission scenarios and explicit protected reserve
guaranteed resource aggregation
capacity-aware allocation across independent alternative groups
personnel generation and incident thresholds
separate towing/carrier and recovery-workload checks
reversible browser storage and JSON import/export
no MissionChief authentication, scraping or mutation

replace remaining Getting Started and Game Systems frameworks
accessible long-page section navigation
mobile-safe tables, code blocks, media and content containment
visible keyboard focus and sticky-heading offsets
complete programme route acceptance on Chromium, iPhone and iPad WebKit
critical WCAG A/AA checks on primary command and interactive surfaces

Stage 42 — v1.4.0 release and completion report

Status: complete when the exact release SHA is deployed and published.

compatible semantic version selected
release metadata advanced to v1.4.0 / Stage 42
release notes and completion report written
public README, Command Centre, API and roadmap reconciled
deterministic exports and generated FAQ synchronised
complete release-grade validation passed
exact release head merged to main
GitHub Pages production deployment verified
immutable annotated v1.4.0 tag and GitHub Release published

Maintenance programme

After v1.4.0, work enters controlled maintenance lanes rather than a new completion backlog:

Upstream drift — changed official missions, resources, documentation or field semantics;
Evidence enrichment — directly reproduced unknown economics, staffing, capacity, training or substitution fields;
Defect correction — canonical, guide, tool, accessibility, CI or production regressions; and
Compatible enhancement — additive guidance or browser capabilities that preserve the v1 contract.

Priority maintenance targets include:

new UK missions, vehicles and game changes through fail-closed drift review;
direct reproduction of currently unpublished infrastructure, vehicle and course fields;
authenticated-interface reproduction of community-candidate resource identities;
continued validation of overlapping alternatives and live substitution behaviour;
routing and geographic optimisation only when suitable location and privacy controls exist;
API compatibility and future versioned releases; and
physical-device checks to complement automated browser coverage.

Definition of complete

A subject is complete only when:

terminology and aliases are searchable;
exact values are verified and dated where published;
dependencies, alternatives, conditions and overlays are explicit;
unpublished and not-applicable fields have explicit decisions;
evidence boundaries are stated;
related documentation and structured records are linked;
validation covers the relevant relationships; and
a player can act without relying on an unexplained assumption.