Project Roadmap¶

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

Core programme status¶

Stages 1–34 are delivered.

62 mission records
46 deployable-resource records
18 infrastructure records
11 qualification records
13 verified mission batches
Static data API v1.0.0

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–20¶

Fire and Rescue baseline and resource integrity
Ambulance and Police alternatives, patients and personnel
Coastguard, Lifeboat, trailer and ocean-rescue modelling
Mountain Rescue resources and explicit mission variants
Search and Rescue HQ, active Drone and missing-person operations
Bomb Disposal infrastructure and initial mission sequence
Airfield Operations, airport infrastructure and Code C/F incidents
Recovery Centres, HGV extensions and structured towing outcomes

Delivered completion programme — Stages 21–34¶

Stage 21 — Railway response¶

Railway Police and Railway fire response infrastructure
Road Rail Unit, EIU, BA support, Foam Unit and DSU resources
Railway Police and command personnel
passenger, goods and station incidents
personnel-range semantics
Railway service guide and Mission Batch 10

Stage 22 — Specialist infrastructure¶

Police Helicopter Station
Public Order, Foam, Pump, Flood and Technical Rescue extensions
Mud Decontamination and Hovercraft extensions
referential enforcement and infrastructure Batch 2

Stage 23 — Qualifications¶

production training schema
eleven verified operational-role records
qualification template and public catalogue
explicit separation of verified roles from unverified course details

Stage 24 — Vehicle economics and staffing¶

structured credit, coin and crew fields
first official Coastguard economics set
market-data evidence standard
comparison-ready export fields

Stage 25 — Bomb Disposal enrichment¶

busy beach and marina progression
small and large railway-station incidents
shed, loft and small building-site incidents
Mission Batch 11 with directory-level evidence boundaries

Stage 26 — Airfield enrichment¶

Stage 27 — Recovery enrichment¶

motorbike and motocross recovery
HGV rollover and hazardous-goods recovery
bus, caravan and major multi-vehicle variants
collision between two buses
Mission Batch 13

Stage 28 — Generated exports¶

deterministic mission, vehicle, infrastructure and training exports
version manifest and search index
validation and deployment integration

Stage 29 — Mission lookup¶

browser-side mission search and service filtering
rendered preconditions, patients and requirement classes

Stage 30 — Comparison¶

deployable-resource comparison
qualification comparison
visible unknown-value handling

Stage 31 — Fleet planning¶

concurrent guaranteed-resource multiplier
independent alternative-group output
explicit scope limitations

Stage 32 — Query catalogue¶

deterministic natural-language keyword matching
cross-collection generated search index
no unsupported generative inference

Stage 33 — Generated FAQ¶

live collection counts
evidence-policy answers
Markdown and JSON outputs generated during builds

Stage 34 — Static API¶

public v1 JSON endpoints
release versioning and manifest
OpenAPI 3.1 contract
API guide and compatibility policy

Ongoing evidence maintenance¶

The numbered core programme is complete. Remaining work is continuous maintenance rather than unfinished architecture:

reproduce additional vehicle prices, staffing and training durations;
verify currently unavailable EOD and Recovery response tables;
add new UK missions and game changes;
test overlapping alternative-resource dispatch allocation;
enrich infrastructure cost, capacity and parent-building data;
maintain API compatibility and publish future versioned releases;
improve tools when new verified fields support transparent calculations.

Definition of complete¶

A subject is complete only when:

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