MissionChief UK v1.4.0

Released: 28 July 2026
Programme: Stage 42
Status: Production
API contract: v1, backwards compatible

v1.4.0 converts the completed evidence and data platform into a full operational command guide. It adds mature service progression for every represented UK emergency-service group, a cross-service account roadmap, alliance doctrine, a local-only readiness planner and a complete mobile/accessibility hardening pass.

Release headline

The guide now answers four connected questions:

1. What does the current UK mission evidence publish?
2. What complete capability chain is required to operate it?
3. How should an account expand without destroying routine reserve?
4. Can the current user-entered inventory handle representative concurrent incidents?

Operational-guide completion

Stage 37A–37I delivers mature evidence-labelled guides for:

• Fire and Rescue;
• Ambulance and HART;
• Police and Public Safety;
• Coastguard and Lifeboat;
• Mountain Rescue;
• Search and Rescue HQ;
• Bomb Disposal and EOD;
• Airfield Operations;
• Recovery and HGV Recovery; and
• Railway Police and Railway Fire Response.

The service estate covers buildings and extensions, vehicles and equipment, personnel semantics, verified training, mission progression, fleet templates, geography, cross-service dependencies, concurrency, common failures and recovery-to-readiness.

Fire mission-family pressure analysis

The Fire programme closes with a live browser-side catalogue analysis that:

• reads the same versioned mission export used by the public API;
• applies transparent overlapping analytical family tags;
• reports guaranteed resource accumulation;
• identifies high single-mission loads;
• preserves alternative slots, patient maxima and personnel fields separately; and
• avoids spawn-frequency or hidden-weight inference.

Cross-service strategy

Stage 38 replaces the strategy frameworks with:

• universal expansion gates;
• Ready, Watch, Degraded, Recovery and Unavailable planning states;
• foundation through mature regional account models;
• a cross-service dependency and handoff matrix;
• urban, rural, coastal and alliance-supported assumptions;
• route-, destination-, access-, cluster-, hub- and relief-base station placement; and
• protected-reserve and recovery doctrine.

Alliance Operations

Stage 39 adds explicit operating modes for:

• ordinary members;
• dispatchers and incident coordinators; and
• alliance administrators.

The guide covers onboarding, least privilege, contribution-policy models, shared infrastructure, mutual-support requests, protected donor reserve, major incidents, events, recruitment, inactivity, moderation and optional external-tool privacy boundaries.

Administrative policy remains clearly separated from game-enforced mechanics.

Account Readiness Planner

Stage 40 adds a local-only browser planning suite that:

• combines several canonical missions and concurrency;
• subtracts explicit protected reserve;
• checks guaranteed resources;
• uses a capacity-aware allocation algorithm for independent alternative groups;
• preserves required-at-incident and available-before-generation personnel separately;
• checks published towing and carrier compatibility in a separate logistics pass;
• reports recovery assets as clearing workloads rather than fictional vehicle rows;
• leaves blank inventory unknown rather than zero;
• stores optional scenarios only in the current browser; and
• supports explicit JSON import and export.

The tool does not authenticate against, scrape or mutate MissionChief.

UX and accessibility

Stage 41 completes the production usability pass:

• remaining Getting Started and Game Systems framework pages are replaced;
• long pages receive collapsed accessible section navigation;
• tables and code blocks own mobile horizontal scrolling;
• content and media remain within the viewport;
• keyboard focus is consistently visible;
• disabled task-list controls receive meaningful accessible labels;
• sticky-header heading offsets are preserved;
• the full service/strategy/alliance/tool route set is accepted on desktop Chromium, iPhone WebKit and iPad WebKit; and
• WCAG-critical checks cover the primary command and interactive surfaces.

Data and API compatibility

The API contract remains v1.

• collection envelopes are unchanged;
• canonical IDs and field meanings remain compatible;
• data publication advances to 1.4.0;
• generated exports continue to be deterministic;
• the official UK mission catalogue remains a separate lossless source surface;
• missing values remain omitted or visibly unknown; and
• no breaking consumer migration is required.

Release evidence snapshot

Collection or state	Count
Official UK missions	1,062
Canonical mission records	1,079
Direct official matches	1,062
Fully canonical official records	1,062
Vehicles and deployable resources	104
Infrastructure records	20
Training and role records	12

Validation

The release candidate must pass:

• complete deterministic data and evidence audit;
• official-catalogue checksum and reconciliation;
• generated export and FAQ equality;
• release-readiness checks;
• link and anchor audit;
• strict MkDocs build;
• JavaScript syntax checks;
• Chromium desktop acceptance;
• iPhone and iPad WebKit route acceptance;
• Account Readiness interactions and local-storage lifecycle;
• critical WCAG A/AA checks; and
• exact-SHA GitHub Pages deployment and production smoke tests.

Remaining evidence boundary

v1.4.0 does not claim that every UK game interface publishes every cost, capacity, staffing rule, class size, course detail, substitution rule or unlock value. Those fields remain unknown until directly reproduced and will continue through the existing evidence, schema and drift-monitoring workflow.