Skip to main content

Overview

Sensor observations, tracks and response plans in one command console.

DomeCommand combines observations from your site's sensors into a shared picture and proposes responses. The operator reviews the evidence and controls which actions may run through the deployment's authority settings.

How it works​

Sensor and aircraft data enters through protocol adapters. Fusion maintains the tracks; rules assess them, and the solver ranks response plans. Each proposed action is checked against the deployment ceiling and autonomy line before it can run. Results feed back into the picture for the next cycle.

EXTERNALINTEGRATIONSENGINEDECISION SUPPORTCOMMANDSENSORSRadar, EO/IR turrets, RF and SDRreceivers, acoustic arrays,Remote ID and ADS-B.AIRCRAFT & EFFECTORSMAVLink autopilots, DJI docks,interceptors, jammers.Commanded back, gated in the engine.PARTNER SYSTEMSSensing pods, from their cloudor ours. Tracks out toTAK and CoT consumers.⇄PROTOCOL ADAPTERSOne adapter per protocol.Everything normalises toobservations, detections andtaskable assets.No proprietary bus.MAVLINKMQTTDJI CLOUDSAPIENTASTERIXMISB 0601ADS-BREMOTE IDSIM▶World modelTracks, assets, zones,one time-aware store.Fusion & trackerFiltered association,confidence, CPA and TTI.SolverOptimisation over assetsand threats, in parallel.Agent hierarchyCopilot, threat, sensor ops,planning, briefing.Scenario & simPlain-language authoring,attached environments.Runs & replayEvery run recorded,replayable, defensible.DISTRI RUNTIMEChannels scope what each agent sees.Connections gate what it may command.▶RULESOne sentence each, withlive fire counts.THE LADDEREvery action at one level,a line and a ceiling.THE LINEWhat runs without asking,what waits for a person.ALERTS & SITREPSPlain language, tracedto the evidence.▶OPERATORMoves the line.Certifiesreleases.Owns everycall thatcommits.RUNS ON ONE WORKSTATION · EVERY ARROW AUDITED
Sensor and aircraft data passes through protocol adapters into fusion, planning and the authority gate.

Sensor fusion​

A radar position and an RF bearing can describe the same object. Fusion associates the observations into one track and keeps the source and age of each measurement with it. A bearing alone does not locate the object; another measurement is needed to resolve its position.

RADARrange, plotEO/IRvideo, MISB 0601RFbearing, emitterADS-Bcooperative positionREMOTE IDcooperative idACOUSTICbearing-onlybearing-only:no fix aloneFUSIONone track per objectone track1 TRACKposition · velocity · classEVIDENCEradar2 sEO4 sRF1 sSix feeds, one track. A bearing alone contributes no fix.

The operator can inspect which sensors contributed to a track and how recently they reported. Read Sensor fusion for measurement types, association and confidence, and Sensors for supported sensor behaviour.

Plans and decisions​

The solver uses the fused picture to rank candidate plans by predicted leakers, cost and coverage under the selected planning profile. Rules can further restrict the actions those plans propose.

The ceiling limits the action levels available in a deployment. The line determines which permitted actions can run without asking. Each action has one of three outcomes:

  • RUNS: it is released and logged, with a stop window where configured.
  • ASKS: it waits for the operator in the DECISIONS queue.
  • NOT PERMITTED: it cannot run under the deployment's authority settings.
PICTUREPROPOSALSDOCTRINEANSWERSFUSED PICTURETRACK 0148tracks in the sectorRULESone sentence eachfacts in, actions outpropose onlyattributed, clampedSOLVERranked planscost · leakage · coveragesame inputs, same planevery plan scoredproposeTHE LADDER0 OBSERVE1 MANOEUVRE2 WATCH3 SHADOW4 DENY5 DESTROYthe ceilingthe linethe line: what runs without askingthe ceiling: what exists here at allNOT PERMITTEDabsent above the ceilingASKSwaits in DECISIONSOPERATORcertifies the callRUNSlogged, stop window

Read Decision support before changing the line. Policy and rules covers restrictions, and Solver configuration covers planning weights. Agentic C2 can read the picture and prepare drafts for review; it cannot change the line or commit actions.

How it works follows one contact through every stage of this loop.

Start with an exercise​

Use Dome Lite to explore the console without connecting hardware. Choose a scenario, load it, and the raid starts with the clock. Follow Simulation, then use Runs & replay to review the recorded picture.

The DomeCommand console during a running engagement
The DomeCommand console during a running engagement
Defenders on the left, two hostile tracks closing on the map, and designation advisories in the decisions queue on the right.

Connect a site​

  1. Create a site. Set its position, geofence and zones.
  2. Choose the environment. Live connections and simulated exercises use separate assets and runs.
  3. Add an asset. Select its product and connection, place fixed sensors and configure any credentials.
  4. Check the picture. Inspect a track's contributing sensors and evidence in Sensor fusion.

Getting started walks through one RF sensor. Integrations lists the supported connections and setup instructions. For an HTTP sensor bridge, use the Signals API.

Deployment and reference​

TaskGuide
Size an on-site serverDeployment
Place detection workloadsRecommended infrastructure
Compare measurement typesSensors
Export rules and constantsDoctrine as a file
Export connections and assetsAsset manifests
Integrate another applicationAPI reference