Mission domain · Taxonomy expansion
Ground-Based Radar: a track is a start, not an answer
A radar return tells you something is there, not what it is or whether it matters. Operators drown in unclassified tracks — birds, weather, and clutter — while the one track that counts scrolls past.
DaggerOS™ treats a ground-based radar as one contributor, not the whole answer. Radar tracks are correlated with RF, EO/IR, and acoustic detections so a return becomes a confirmed, classified object with a confidence, not an unresolved blip. The operator sees fewer, better tracks. BlackEcho™ flags what deserves attention first.
How DaggerOS handles it
Radar excels at range and coverage and is weak at identity. DaggerOS pairs each radar track with independent evidence from other domains, so classification comes from behavior across sensors rather than from a single return. Clutter and low-value tracks fall away; the tracks that persist and correlate rise. Nothing is acted on until a human sustains the Human Gate.
Related subsystems
- DaggerOS — correlates radar tracks with the rest of the picture and records the decision.
- BlackEcho — prioritizes tracks and drafts a recommendation for the operator.
- Human Gate — the single authorization point.
Standards touched
Engineered to consume radar and surveillance track data in ASTERIX categories and ground-moving-target indication aligned to STANAG 4607, and to exchange tasking through a NATO SAPIENT-aligned interface. Decision authority is held to DoDD 3000.09.
Where it fits
Ground-based radar underpins base air defense and border surveillance, where wide-area coverage must be turned into a small number of decisions. It matters most to program offices and installation defenders standing up a layered sensing picture. See base air defense and border surveillance.
Evidence
Roadmap. Radar-track fusion is a planned expansion of the demonstrated multi-sensor picture; it is not yet shown as a standalone capability, and we mark it honestly.
FAQ
Do you build the radar?
No. DaggerOS is radar-agnostic. It consumes tracks from fielded radars and fuses them with other domains rather than replacing the sensor.
Why fuse radar with other sensors at all?
Because a radar track rarely tells you identity or intent. Correlating it with RF, EO/IR, and acoustic evidence turns a blip into a classified object an operator can decide on.
What track formats are supported?
The design targets standard surveillance track formats such as ASTERIX and STANAG 4607 GMTI so existing radars can contribute without a custom bridge.