Unclassified // Public Release · Capability outcomes only
The platform

One operator. Every domain. One record.

DaggerOS turns many passive sensors into one picture, proposes a response, and waits. The call is always a person’s — and the record proves it. Below is the whole loop, and a way to hold the gate yourself.

Air-gapped by architecture Human-in-command Evidence-first TRL 7–8
Operator Night · live, in your browser

When every domain hits at once, one operator holds the picture.

Threats arrive across air, spectrum, sea, ground, space and the network — together. The machine proposes a response for each and queues it. Nothing commits until you hold the gate. Authorize the calls you agree with, dismiss the ones you don’t, and watch the record build. It runs entirely on this page, with zero network calls — the same posture as the box.

LIVE SCOPE · ON-BOX
MISSION CLOCK 00:00AUTONOMOUS ACTIONS 0
Decision queue0
Standing by…
Proposals will queue here. Nothing acts without you.
0Proposals surfaced
0Authorized by you
0Dismissed
0Autonomous actions
Decision record · SHA-256 chained · tamper-evident

A demonstration of doctrine, not a product screen. The real system fuses live sensors and runs the same loop on the box, offline. How the human gate works →

The decision loop

Five steps. One of them is a person.

Every effect DaggerOS can propose travels the same path. Each step says what happens, not how — the how stays on the box.

01 · SENSE

Listen first

Passive sensors across domains take in the environment without announcing themselves. Quiet by default; emit only on a human’s call.

02 · FUSE

One picture

Separate returns that describe the same thing are resolved into a single track. Operators see one shared picture instead of a dozen screens disagreeing.

03 · PROPOSE

Recommend, with reasons

The on-box AI proposes an action and shows its reasoning and confidence. Sense to proposal takes about 6 ms. It never reaches past the recommendation.

04 · HUMAN GATE

A person decides

A human holds a deliberate gate to authorize — or doesn’t. There is no autonomous engagement path and no way to configure one. This is the step that cannot be automated away.

05 · RECORD

Written down, for good

Who decided what, when, and on what evidence is written to a SHA-256 chained record. Change one entry and every seal after it breaks. History can’t be quietly rewritten.

See DaggerOS in full →

Measured, not claimed

What the loop holds to.

7–8TRL
Demonstrated at T-REX 26-2 (May 2026) — live and operationally representative, with third-party observation.
~6ms
From sense to proposal on the box. Fast enough to keep a person ahead of the problem, not replace them.
0
External network calls. The full loop runs on the box, air-gapped by architecture.
100%
Gate-verified decisions — zero rollbacks. Nothing committed an effect without a human.
10
Mission domains fused into one picture on one platform.
7,000+
Intercept-safety trials with zero safety violations recorded.
0
Autonomous engagement paths — by design, and not configurable.
∞
Reach-back required: none. It keeps working in denied, degraded, intermittent and low-bandwidth conditions.

Figures are directional and reflect public-release posture. Cost-asymmetry and threat figures are attributed on the counter-UAS economics page.

How it’s built

Four commitments the architecture keeps.

Air-gapped by architecture

Not a setting you can forget to turn on. The loop closes on the box with no external calls, so there is no cloud to lose, no link to jam into uselessness, and nothing phoning home with your data.

Passive by default

DaggerOS listens before it ever emits. It gives away nothing about where it is or what it sees until a human decides to act. Quiet is the default state, not a mode.

Evidence-first

The record isn’t a log file bolted on afterward. Decisions, evidence and authorship are chained with SHA-256 as they happen, so an after-action review has something that holds up.

On-box AI that recommends only

BlackEcho is an offline co-pilot. It explains the picture and proposes a response in plain language. It never takes the action — that authority stays with the operator.

Fits what you already run

Open where it counts. Closed where it matters.

DaggerOS is a mature, open component, engineered to drop into the systems and acquisition paths you already use — without opening the box to the network.

  • Interoperates with MAVLink, ArduPilot and PX4 autopilot ecosystems.
  • Shares a picture over ATAK / Cursor-on-Target and NATO SAPIENT.
  • Acquirable through FAR Part 12, Other Transaction Authority, and SBIR Phase III.
  • Firm-fixed-price friendly; under DFARS 227.7202 the government owns its mission data.

For integrators → Acquisition paths

GOVERNANCE POSTURE

Human-in-command, on the record

DaggerOS is engineered to align to DoD Directive 3000.09 on autonomy in weapon systems and the DoD AI Ethical Principles. A person is always in command of any effect, and the authorization is written to the record.


“Aligned to” and “engineered to” describe design intent. BlackByrne does not claim a granted ATO, FedRAMP authorization, CMMC certification, program of record, or any DoD endorsement.

Straight answers

Platform FAQ

What is the DaggerOS decision loop?
Passive sensors across domains fuse into one picture; the on-box AI proposes an action with its reasoning and confidence; a human authorizes at a single gate; and the decision is written to a tamper-evident, SHA-256 chained record. There is no autonomous engagement path.
Does DaggerOS act on its own?
No. The AI recommends; a human decides. Nothing commits an effect without a person holding the authorization gate — consistent with DoD Directive 3000.09 and the DoD AI Ethical Principles. The autonomous path does not exist and cannot be configured.
How is it air-gapped?
DaggerOS is air-gapped by architecture and passive by default. The full loop runs on the box with zero external network calls, so it keeps working in denied, degraded, intermittent and low-bandwidth (DDIL) conditions — and your data never leaves.
What is Operator Night?
The demonstration above. Threats arrive across several domains at once, the machine proposes a response for each, and you authorize or dismiss one call at a time onto a tamper-evident record. It runs entirely in your browser with no network calls — a small, honest model of how the real system behaves.
Can I see it for real?
Yes. Request a demonstration and we will show the loop on the box, offline, against a mission that spans domains.
Keep Watch. Keep Command. ♦

Bring us the mission that spans domains.

We will show you the whole loop — sense, fuse, propose, and the gate you hold — on the box, offline.