Introduction · How it works
One contact, all the way through
Follow a single drone from the first detection to the record of what happened. Every stage is a seam with a contract, which is what makes any of it replaceable.
DomeCommand is the layer between your sensors and your effectors. Its job is turning a chaos of raw detections into a decision somebody can make in seconds.
That job is one loop, and it never stops.
The vocabulary, in order
These are the words the product uses. Each is a real stage with a real output.
| What it is | |
|---|---|
| Observation | One detection, from one sensor, in one modality. The rawest typed input. |
| Track | A fused estimate of one object over time: position, velocity, classification, threat score. |
| Frame | A per-tick summary of the current picture, by sector. |
| Alert | A rule-triggered warning with a lifecycle. Edge-triggered, so it is not re-emitted every tick. |
| Sitrep | A narrative assessment of recent frames, written by the agent. |
| Course of action | A ranked response, produced by the solver and gated by authority. |
| Engagement | Execution of an authorised action against a target. |
| BDA | What actually happened. |
Walk one drone through it
A radar returns a plot. That is an observation. It carries a position, an uncertainty and which sensor produced it. Seconds later an RF direction-finder produces a bearing with no range at all, and an acoustic node reports a zone.
Fusion makes them one track, because their geometry is consistent. Agreement is not the test; three sensors can agree and still be wrong about the same thing. The track carries a confidence that reflects how many independent sources support it and how recently. See Sensor fusion.
A frame summarises the tick. How many contacts, in which sectors, closing how fast.
A rule fires. The track is inside a keep-out zone and its affiliation is not friend, so it is designated SUSPECT and an alert opens. This is the fast loop, and it runs every tick.
The slow loop assesses. The agent reads recent frames and writes a sitrep in plain language. This is gated rather than continuous, because narrative assessment is expensive and the fast loop must not wait for it.
The solver authors plans. Each is scored on predicted leakers, cost and coverage, and ranked. See Solver configuration.
Authority decides whether anything runs. The posture in force sets a gate on each effect the plan proposes. Cue a sensor is probably AUTO. Intercept is probably not. See Decision support.
Something is engaged, and assessed. The result is recorded, the picture updates, and the next cycle adapts.
Two loops, nested
| Runs | Does | |
|---|---|---|
| Fast, reflexive | Every tick | Ingest, fuse, frame, fire rules, raise alerts |
| Slow, cognitive | Gated | Assess, narrate, plan, recommend |
The fast loop must never wait for the slow one. An alert about a geofence breach cannot be held up because a narrative assessment is still being written.
Every feed, by what it measures
The console can show every sensor feed at once, each rendered by its modality: a waterfall for RF, video for a camera, a report for a detector that only says something is there.
Every stage is a seam
Each stage has a contract, and the wire format strings are frozen. Change the internal representation as much as you like; the schema string never changes.
That is what makes a new sensor an adapter rather than a rewrite, a new fusion algorithm a swap behind a trait, and a new effector a port. It is also why DomeCommand can be sensor-agnostic and effector-agnostic without that being a marketing claim: nothing above the ingestion layer knows what produced an observation.
What is real, and what is modelled
The fusion and tracking mathematics, the layered pipeline and its contracts, threat scoring, authority gating, the solver, the API and the console are all real. The protocol decoders are real decoders.
Effectors are modelled, not wired to hardware, and kinetic action is gated behind a human at every posture a commercial site can reach.
Where to go next
- Sensor fusion, where the picture comes from.
- Decision support for who may say yes.