Additional modules
Three directions the platform extends in. All three are concepts today, shown as direction rather than as something you can order.
None of the three modules below ships today. They are the direction the platform extends in, and they are described here so you can see where it goes. The core product, everything else in these docs, is what exists.
| Module | What it is | Where it runs |
|---|---|---|
| Dome Node | Edge autonomy for interceptors and patrol drones | On the airframe |
| Dome CSI | WiFi presence sensing for civil missions | On a carried pod |
| Dome Acoustic Array | A low-cost acoustic detection net | On masts, in bulk |
Dome Node
A companion module that rides an interceptor or a patrol drone. A slice of the fusion engine runs on the airframe, so the aircraft keeps its own picture when the link degrades and flies the specific task it was given.
| Onboard | Fusion and filtered tracking over the aircraft's own sensors, holding a local slice of the world model |
| Tasking | Specific jobs from the dome: intercept this track, hold this box, follow and report. Each arrives through the gate set for its effect class. |
| On link loss | Completes the last approved task on its own picture, then holds. It never self-authorises a new effect. |
| Integration | MAVLink to the autopilot, the same protocol layer the dome already speaks |
We build the module and the loop, never the interceptor. It plugs into airframes that already exist. Ukrainian interceptors carry onboard terminal guidance today at $2,000 to $3,500 a unit, which is the class this is designed to sit on.
Dome CSI
WiFi signal sensing carried on a drone. Presence, movement and activity read from ordinary wireless signals, with no cameras, feeding the same fused picture as every other sensor.
| Missions | Search and rescue, disaster response, clearing a structure before entry |
| Sensing | Presence, movement and activity from standard WiFi and RF. No cameras, no imagery, no emitters placed on the ground. |
| Connectivity | The pods mesh sensor to sensor with no internet connection, which is what makes carrying them to a disaster site workable |
| Into the picture | Detections join fusion through the existing partner integration, alongside radar, RF and acoustic |
| Action catalogue | Civil only. Locate, mark, report, cue rescue teams. No effects. |
Fly the structure, map the people inside, and hand the team a picture instead of a guess.
This is built on partner technology that ships today: API-delivered, self-calibrating per site, running on ordinary routers.
Dome Acoustic Array
A low-cost acoustic sensor designed for bulk production. One node hears what radar misses at low altitude. A net of them covers a corridor, a border or a city.
| Detection | Acoustic signatures of Shahed-class and smaller uncrewed aircraft |
| Output | Bearings and tracks over the sensor buses the dome already speaks, into fusion like any other sensor |
| Cueing | Fusion slews EO/IR onto each acoustic track for classification, which closes the gap every acoustic network has: hearing is not identifying |
| Cost class | $400 to $1,000 a node |
The precedent is public. Ukraine's Sky Fortress fielded around 14,000 nodes in that cost class; a comparable network reports detection to national picture in twelve seconds. One documented raid: 84 drones heard, 80 brought down.
Why these three
Each one extends a different edge of the same loop.
- Dome Node carries the loop outward, onto the airframe, so degradation of the link does not degrade the aircraft's understanding.
- Dome CSI extends what the picture can contain, to people inside a structure, and it is the clearest case of the same software serving a civil mission with a different action catalogue.
- Dome Acoustic Array extends coverage downward in cost, which is the only way wide-area detection becomes affordable at national scale.
Where to go next
- Sensor types for the sensors available today.
- Deployment for what the core runs on.