Mission domain · Published capability
Ground Robotics: the robot senses and carries, the human decides
Uncrewed ground vehicles put a sensor or a tool where a person should not go — a suspected device, a breached perimeter, a contaminated zone. The risk is autonomy creeping past the point where a human is still deciding what the machine does.
DaggerOS™ treats an uncrewed ground vehicle as both a moving sensor that feeds the picture and an effector the operator can task — always with the human in command. Over open, MOSA-aligned interfaces it is airframe- and platform-agnostic. BlackEcho™ can recommend how to use the platform, but the vehicle takes no consequential action without the Human Gate.
How DaggerOS handles it
A ground robot is most useful where a human should not be, which makes the authority question sharp: the machine must not decide the consequential act on its own. DaggerOS keeps the operator in command — the platform’s detections join the fused picture, and any effect it delivers passes the Human Gate. Integration is over open interfaces, so DaggerOS adapts to the platform rather than the reverse.
Related subsystems
- DaggerOS — fuses the platform’s sensing into the picture and gates its effects.
- BlackEcho — recommends how to employ the platform; it never commands it autonomously.
- Human Gate — the single authorization point for any consequential action.
Standards touched
Control and telemetry integrate over MAVLink and align to STANAG 4586 for uncrewed control interfaces; sensing joins the picture per NATO SAPIENT. Human-in-command is held to DoDD 3000.09 — no autonomous engagement path.
Where it fits
Ground robotics supports installation force protection, counter-IED and EOD stand-off, and CBRN reconnaissance. It is evaluated by SOF elements, program offices, and prime integrators. See installation force protection and the prime integrators view.
Evidence
Roadmap. UGV integration over open interfaces is a planned capability and is marked honestly as not yet demonstrated.
FAQ
Does the robot act on its own?
No. It senses and it can be tasked, but any consequential effect passes the Human Gate under DoDD 3000.09. There is no autonomous engagement path.
Which platforms does it work with?
It is platform-agnostic over open, MOSA-aligned interfaces such as MAVLink and STANAG 4586, so DaggerOS adapts to the vehicle rather than requiring a specific one.
What is the point of a robot that still needs a human?
To put a sensor or a tool where a person should not go while keeping a human deciding the consequential act. Reach without ceding authority is the whole idea.