Game Systems

Game systems connect the canonical mission, resource, infrastructure and personnel records. Use this section when a problem affects several services rather than one fleet.

System command map

System	Operational question	Primary guide
Mission generation	Why can this incident appear?	Missions and Dispatching
Requirement semantics	Is a resource guaranteed, alternative, conditional or probabilistic?	Missions and Dispatching
Buildings and extensions	Does infrastructure generate missions or provide response capability?	Buildings and Extensions
Personnel and qualifications	Is a vehicle or role operationally staffed?	Training and Personnel
Patients and transport	Will treatment, transport and destination turnaround exhaust cover?	Ambulance and HART
Prisoners and custody	Can scene response and custody transport remain independent?	Police and Public Safety
Towing, trailers and carriers	Is the complete logistics chain deployable?	Vehicle Catalogue
Geography	Will resources reach incidents, access points and destinations?	Station Placement
Cross-service readiness	Can all hard partner services operate concurrently?	Account Progression
Alliance contingency	Is external support governed and sustainable?	Alliance Operations

Evidence model

The production platform keeps these layers separate:

Generation preconditions
        ↓
Mission requirement semantics
        ↓
Deployable resource and personnel contracts
        ↓
Patient / prisoner / recovery outcomes
        ↓
Geographic and destination cycle
        ↓
Return to operational reserve

A failure can occur at any layer. Buying another vehicle will not correct a missing extension, unavailable qualified role, incomplete towing chain, distant destination or consumed reserve.

Canonical semantics

Unknown is not zero

Missing cost, capacity, staffing, course or unlock data remains unknown. It must not be treated as free, unlimited or unnecessary.

Generation is not dispatch

A building, extension, active equipment item or available-personnel threshold can permit mission generation without becoming a dispatched resource row.

Ownership is not readiness

A resource should count as operational only when it is correctly located, staffed, trained and able to fulfil its complete logistics chain.

Outcomes are not vehicle requirements

Patient, prisoner and recovery fields describe work produced by an incident. They are not automatically converted into fictional vehicle quantities.

Operational tools

• Mission Lookup — inspect one current canonical mission;
• Account Readiness Planner — compare several incidents with user-entered inventory and reserve;
• Resource Comparison — compare populated canonical resource or qualification fields;
• Concurrent Fleet Planner — multiply published guaranteed quantities;
• Query Catalogue — retrieve evidence across all canonical collections.

Service-specific application

The Emergency Services index applies these systems to Fire, Ambulance/HART, Police, Coastguard/Lifeboat, Mountain Rescue, SAR HQ, Bomb Disposal, Airfield, Recovery and Railway operations.