Mission Requirement Lookup

Search the complete official MissionChief UK mission catalogue alongside the higher-trust canonical records maintained by this project. The lookup covers mission IDs, names, aliases, POIs, categories, generating services, official requirement keys and generation prerequisites.

Search

Loading the official UK mission catalogue…

Current coverage

1,062 official UK missions
1,079 canonical mission records
1,062 direct official/canonical ID matches
1,062 fully canonical missions
0 official missions awaiting direct canonical records

The full five-gate position and per-mission blockers are published on the Mission Verification Status page.

Evidence levels

The lookup deliberately distinguishes the source and normalized evidence tiers:

• Official catalogue — the mission exists in the current public MissionChief UK catalogue and its official raw requirement keys are shown verbatim.
• Canonical mapped — a project record has been normalized into verified resources, probabilities, alternatives, personnel, patients and preconditions where those fields have been reproduced.
• Fully canonical — the record has passed identity, official-key mapping, operational and final evidence-completeness gates in the verification programme.

An official catalogue record is authoritative evidence that the mission and displayed official fields exist. It is not automatically a verified dispatch recommendation. Unknown internal keys are never guessed into vehicle types.

Canonical interpretation

Canonical records distinguish:

• guaranteed resources;
• probability-based resources;
• conditional resources;
• independent alternative groups;
• generation preconditions;
• patient and prisoner ranges;
• personnel requirements;
• evidence status and verification date.

An empty dispatch table means that dispatch-level evidence is not published for that canonical record. It does not mean that no response is required.

Verification programme

Every mission progresses through:

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

The machine-readable status exposes every mission’s current stage, canonical path, blocking reasons and next action. A mission can only enter a mapped stage when every official requirement, chance and prerequisite key it uses is present in the verified key registry.

Data sources

The tool and supporting verification pages consume:

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

The official catalogue is refreshed from https://www.missionchief.co.uk/einsaetze.json, checksummed, reconciled against canonical IDs and committed through an isolated ingestion workflow. Every complete raw official object remains retained under data/sources/missionchief-uk/ for audit and future mapping.