MissionChief UK v1.1.0

Released: 24 July 2026
Release type: Mission intelligence expansion
Static Data API: v1, backwards compatible

MissionChief UK v1.1.0 expands Mission Lookup from the original 62 canonical records to the complete public United Kingdom mission catalogue, begins the enforced programme to reach 100% fully canonical coverage and preserves a strict distinction between official source data and normalized operational evidence.

Mission catalogue baseline

1,062 official UK mission records
284 canonical mission records
267 official IDs matched to canonical records
226 fully canonical mission records
795 official records awaiting direct canonical records
17 canonical overlay or derived records without standalone official IDs
48 canonical deployable-resource records
18 canonical infrastructure records
12 qualification records
Static Data API v1.1.0

The official source snapshot is retained with URL, retrieval time and SHA-256 provenance. Every published top-level and nested mission field is preserved.

Added

• Complete lossless official UK mission catalogue with 1,062 records.
• Search across official IDs, names, POIs, generators, categories, requirements and prerequisites.
• Service/generator and evidence filters in Mission Lookup.
• Separate canonical and official evidence states.
• Structured views for patients, personnel, duration, follow-ups, expansions, overlays, variants and additional fields.
• Complete official JSON viewer for every mission.
• Public catalogue, reconciliation and verification endpoints.
• Deterministic source coverage, key inventories and integrity auditing.
• Content-addressed daily refresh and Pages deployment only when source or verification state changes.
• Cross-browser acceptance for completeness, search, structured metadata, raw records and horizontal containment.

100% verification programme

Every mission progresses through:

1. captured;
2. identity verified;
3. requirements mapped;
4. operationally verified; and
5. fully canonical.

The release includes:

• base and scalable batch verification registries;
• an official-key mapping registry;
• deterministic blockers and next actions;
• aggregate promoted-mission identity diagnostics;
• strict chance-aware key-equivalence validation;
• offline coverage reconciliation after every canonical batch;
• evidence-safe candidate and official-key backlog analysis across all 1,062 records;
• a generated public verification endpoint; and
• a generated verification-status page.

The first 30 fully canonical batches contain:

Batch 1: 0, 1, 2, 3, 4, 6, 7, 8, 9, 10,
         11
Batch 2: 13, 14, 15, 16, 17, 18, 19, 23, 24, 27
Batch 3: 32, 58, 65, 202, 203, 313, 334, 352, 365, 366,
         388, 399, 400, 421, 435, 468, 472, 475, 535, 541,
         570, 577, 624, 638, 668, 772, 857, 858
Batch 4: 21, 22, 31, 301, 353
Batch 5: 232, 236, 317, 401, 481, 482, 513, 517, 575, 597,
         669, 849, 850, 851, 852
Batch 6: 59, 139, 314, 404, 815, 824
Batch 7: 107, 153, 175, 178, 248, 249, 250, 402, 406
Batch 8: 169, 177, 243, 244, 256, 518
Batch 9: 180, 251, 469
Batch 10: 134, 579
Batch 11: 30
Batch 12: 12
Batch 13: 127, 392, 419, 440, 441, 466, 476, 477, 670, 682,
         775, 841
Batch 14: 703
Batch 15: 420
Batch 16: 734, 735
Batch 17: 20, 25, 64, 75, 108, 168, 171, 204, 241, 255,
         268, 315, 320, 323, 324, 325, 326, 327, 328, 330,
         333, 362, 367, 369, 371, 372, 373, 375, 396, 397,
         422, 423, 470, 473, 514, 515, 516, 606, 607, 626,
         639, 662, 666, 667, 678, 683, 685, 686, 723, 724,
         725, 727, 774, 798, 804, 840, 847, 856
Batch 18: 149, 189, 233, 242, 394, 398, 403
Batch 19: 527, 528, 602, 704
Batch 20: 408, 409, 410
Batch 21: 72, 805, 823
Batch 22: 749, 793, 794, 795
Batch 23: 507, 519, 828
Batch 24: 300
Batch 25: 625, 677, 718
Batch 26: 29, 69, 73, 90, 126, 128, 129, 130, 131, 133,
         322, 393, 442, 443, 444, 451, 467, 478, 484, 485
Batch 27: 687, 688, 717, 733
Batch 28: 806
Batch 29: 810
Batch 30: 565

All 226 promoted missions pass exact official identity, aggregate diagnostics and strict key equivalence. The current analyser has exhausted every mission covered by the verified mapping contract and reports zero immediately safe records; the next phase requires another verified official-key mapping.

Accuracy controls

• Official values are preserved verbatim.
• Unknown internal keys remain visible and are never guessed.
• Canonical records remain the higher-trust dispatch model.
• Seasonal availability, base missions, overlays and variants remain distinct.
• New official fields are retained automatically.
• Duplicate IDs, missing names, stale reconciliation, stale inventories and source/public mismatches fail validation.
• A mission cannot enter a mapped gate while any official requirement, chance or prerequisite key is unclassified.
• not-applicable mappings require narrow allowed values.
• Strict missions must exactly match mapped official quantities, probabilities and canonical preconditions.
• Aggregate diagnostics report every promoted identity or mapping failure in one run.
• Unresolved relationship IDs block fully canonical promotion.
• Self-referential base identities remain distinct from genuine variants.

Public data additions

api/official/uk-missions.json
api/official/uk-mission-coverage.json
api/official/uk-mission-verification.json

These endpoints remain separate from the canonical api/v1/ contract. Existing v1 paths, envelopes, IDs and evidence semantics remain compatible.

Automated maintenance

The official refresh runs daily and may be dispatched manually. An unchanged source SHA and unchanged verification state produce no repository change. Changed data must pass importer validation, publication, compaction, coverage reconciliation, registry merge, aggregate identity diagnostics, key mapping validation, candidate and key-backlog analysis, and catalogue auditing before commit and deployment.

Validation sequence

The release is eligible only after:

1. canonical schema and relationship validation;
2. official/canonical coverage reconciliation;
3. official catalogue losslessness validation;
4. verification batch registry merge;
5. aggregate promoted-mission identity diagnostics;
6. official-key mapping and strict chance-aware equivalence validation;
7. evidence-safe candidate and key-backlog analysis;
8. deterministic verification-status generation;
9. export and FAQ generation;
10. repository, API, link and anchor auditing;
11. strict MkDocs and built-site auditing;
12. JavaScript and Chromium acceptance;
13. GitHub Pages deployment;
14. live HTTP and public-data smoke testing; and
15. Chromium, Firefox, iPhone WebKit and iPad WebKit acceptance.

Independence

MissionChief UK is an independent community project maintained by Conroy1988. It is not operated by, endorsed by or affiliated with SHPlay GmbH or the official MissionChief team.