Mission domain · Published capability
Space Domain Awareness: what passes overhead is context
What passes overhead shapes what happens on the ground — an overflight can cue a strike or a collection window. Yet overhead awareness usually lives in its own stovepipe, disconnected from the operator making the ground decision.
DaggerOS™ treats overhead awareness as context in the same picture the operator uses for air and ground decisions, rather than a separate feed. Knowing what passes above a site, and when, informs how much to trust a sensor window or an emission pattern below. BlackEcho™ ties overhead timing to activity on the ground where a correlation exists.
How DaggerOS handles it
The contribution of space domain awareness is correlation: an overhead pass is a timing cue for what happens beneath it. DaggerOS places that context beside the RF, radar, and EO/IR pictures so the operator reasons about cause across domains rather than watching orbits in isolation. It stays air-gapped and on-box. The overhead picture informs decisions; it never triggers one — the Human Gate governs any effect.
Related subsystems
- DaggerOS — correlates overhead context with the ground and air picture and records it.
- BlackEcho — surfaces overhead timing that lines up with observed activity.
- Human Gate — the single authorization point.
Standards touched
Security and provenance align to NIST RMF 800-37 and hashing per FIPS 180-4 / 186-5; tasking and track exchange follow NATO SAPIENT. Human authority is held to DoDD 3000.09.
Where it fits
Space domain awareness supports critical-infrastructure protection and force protection, where overhead timing matters to a ground decision. It is evaluated by program offices and coalition partners. See critical infrastructure protection and the program office view.
Evidence
Roadmap. Overhead-context correlation is a planned expansion of the fused picture and is marked honestly as not yet demonstrated.
FAQ
Does DaggerOS track satellites itself?
It is designed to consume overhead awareness and correlate it as context, not to replace a space surveillance network. The value is tying overhead timing to ground and air activity.
Why put space data in front of a ground operator?
Because an overflight can be the reason an emission pattern or a collection window appears below it. Correlating the two gives the operator cause, not just effect.
Does overhead data leave the box?
No. Like every domain, it is processed on-box within the air-gapped architecture.