Buildings and Extensions Database
The production infrastructure database contains 20 schema-controlled records used by verified mission preconditions and planning relationships.
Production location
Section titled “Production location”data/uk/infrastructure/Canonical records
Section titled “Canonical records”| Canonical ID | Name | Kind | Verified mission effect |
|---|---|---|---|
airfield_operations_extension | Airfield Operations Extension | Extension | Airfield-operations generation |
aviation_firefighting_extension | Aviation firefighting Extension | Extension | Airport-firefighting generation |
beach_lifeguard_extensions | Beach Lifeguard Extension | Extension | Beach-lifeguard generation |
bomb_disposal_hq | Bomb Disposal HQ | Building | Bomb Disposal generation |
bomb_disposal_marine_unit_extension | Bomb Disposal Marine Unit Extension | Extension | Coastal Bomb Disposal generation |
container_extension | Container Extension | Extension | Container vehicle purchase and storage |
flood_rescue_extension | Flood Rescue Extension | Extension | Flood-rescue generation |
foam_extension | Foam Extension | Extension | Foam-dependent generation |
hart_base | HART Base | Building | HART-dependent generation |
hgv_recovery_extension | HGV Recovery Extension | Extension | Heavy-vehicle recovery variations |
hovercraft_extension | Hovercraft Extension | Extension | Hovercraft-dependent generation |
mass_casualty_extension | Mass Casualty Extension | Extension | Mass-casualty generation |
mud_decontamination_extension | Mud Decontamination Extension | Extension | Mud-rescue generation |
police_helicopter_station | Police Helicopter Station | Building | Police air-support generation |
police_public_order_extension | Police & Public Safety Extension | Extension | Public-order generation |
railway_fire_response | Railway fire response | Building | Specialist rail-fire generation |
railway_police | Railway Police | Building | Railway Police generation |
recovery_centre | Recovery Centre | Building | Recovery missions and variations |
technical_rescue_extension | Technical Rescue Extension | Extension | Technical-rescue generation |
water_damage_pump_extension | Water Damage Pump Extension | Extension | High-volume pumping generation |
Referential integrity
Section titled “Referential integrity”Mapped mission fields are validated against these canonical IDs. A mission fails validation when it claims a countable specialist precondition without a matching infrastructure record.
Infrastructure is not a dispatched resource
Section titled “Infrastructure is not a dispatched resource”A generation precondition does not automatically prove:
- that a vehicle from the building must attend;
- the building’s vehicle capacity;
- staffing or classroom capacity;
- purchase price or construction duration; or
- whether an extension is active by default.
Examples:
- Mass Casualty Extension is separate from Mass Casualty Equipment.
- Recovery Centre is separate from the number of assets to tow.
- Airfield Operations Extension is separate from Airfield Operations Vehicles.
- Active Drone counts are generation state, not automatically a Drone dispatch row.
Complete evidence disposition
Section titled “Complete evidence disposition”Release v1.4.2 resolves all 80 tracked fields—cost, build time, capacity and compatible parent building for every record—without inventing values:
- 9 verified fields carry a directly published value;
- 65 not-published fields record that the checked official source set does not publish a value; and
- 6 not-applicable parent fields belong to standalone buildings.
Published detail currently includes the HART Base and Police Helicopter Station costs and maximum expansion levels, plus the Police & Public Safety Extension cost and dedicated Detention Van space. Three extension records also have verified parent-building relationships. A not-published field never means zero, free, instant, unlimited or unavailable.
The schema and semantic validator require all four evidence decisions on every record. A missing decision, a verified field without a value or an unpublished field carrying a value fails validation.