Use case 03 / Critical infrastructure
The site you already have.
The same fused picture and the same decision loop, on the sensors the site already owns, with every effect gated for civil law.
The site's own sensors
ASTERIX, MISB, MQTT, SAPIENT, ADS-B
Detection runs free
Effects wait for a named authority
One small board
Server, console, simulator, database
On 5 August 2026 a drone carrying explosives closed Leipzig Halle, one of Europe's largest cargo hubs. Airports, refineries, ports and power plants face the same aircraft the military faces, with two extra constraints. The sensor estate is whatever the site already bought, and civil law decides what a defender may do about a contact.
Runs on what the site has
A deployment binds the protocols the site's equipment already speaks. Existing radar over ASTERIX, cameras over MISB video metadata, sensors over MQTT and SAPIENT, cooperative aircraft over ADS-B and Remote ID. Day one needs adapters, not a new sensor suite.
Detection runs free, effects wait
Detection, classification, alerting and sensor cueing run automatically. Everything above them waits for a named authority, because at a civil site the honest state of most effects is withheld. The authority is not the operator's to exercise.
Evidence by construction
Every detection, designation and alert traces to the observation that produced it, and every run is recorded and replayable. For a site that answers to a regulator, the record is the point.
Sized for a site
The whole deployment (server, console, simulator and database) runs on one small board in a cabinet, close to the sensors, and keeps working when the link out is poor.
Where to go next
- Ingesting data for connecting the site's sensors.
- Policy and rules for authoring the site's doctrine.
- Recommended infrastructure for the reference node and where each workload sits.