Layout

The system is four messages on a roof.

Everything else may differ: camera, mic, radar, net, balloon, mother drone. The messages stay.

01 · The four messages

DETECTION

Sensor node → cell. I heard or saw something. Here is my bearing, time, quality. Never a finished position.

TRACK

Cell → nodes. Several detections became a track. Here it is.

TASKING

Cell → chosen interceptors. Launch clearance, target, role in the pack. Arming is never this message.

OUTCOME

Interceptor → cell. Caught, missed, aborted.

Field names and encoding are still open. The split is not. The Frankfurt simulation already runs this chain: three bearings make a track, ten interceptors per inbound, a net, a receipt, no explosion.

02 · Layers

Roof

Citizen node. Scanner first, interceptor optional. Cheap, many, replaceable.

Cell

Fusion and tasking per neighbourhood, not per country. If the cell dies, the nodes still sit there.

Second layer

Fire brigade and THW: longer sensors (Aaronia, SPEXER), stronger interceptors. Same protocol.

Airborne later

Mother drones, weather balloons, a Quantum Vector as a high ear. Same DETECTION message, different altitude.

Fakten-Tabelle · Fact table

Fakt

The Wunderglobe simulation requires at least three bearings for a track and ten interceptors per inbound. Simulation values, not a vendor sheet.src/stachelschweinMath.js

Hypothese

Cell size, time sync without GPS on every node, false alarms, legal idle vs armed: open, system design 7 September 2026.docs/systementwurf.md