Nobody flies BLIS-D. The doctrine does. The pilot’s seat in this platform is occupied by an operating loop — CBRN-CADS — and understanding why that architecture was chosen explains most of what makes unmanned CBRN response credible at all.

A joystick is a liability in a hot zone
Remote piloting assumes a stable link, a calm operator, and time. A chemical release scenario denies all three. Doctrine-led flight inverts the design: the platform executes a pre-validated operating loop — detect, identify, assess, task, decon — and the human enters the chain only at the two gates where judgment outperforms procedure: assessment and tasking.
This is not autonomy for its own sake. It is the recognition that in a CBRN event, the scarcest resource is not lift or sensor range — it is defensible decisions per minute.
Five gates, ninety seconds
The loop’s value is its sequence discipline. Detection without identification triggers nothing; identification without assessment tasks nothing. Each transition is logged as a structured entity — our design goal is full auditability of every gate, so that the after-action question “who decided what, on which reading, at which second” has a machine answer.

What the ops board actually watches
The board above is a mock of the operating view: sorties against plan, detection events, decon cycles, and — the number that matters — loop latency. When latency drifts up, the cause is almost never the airframe. It is a gate: an assessment queue backing up, a tasking rule too conservative for the day’s wind. Doctrine-led platforms fail at the doctrine layer, which is exactly where you want failures — visible, loggable, fixable.
The doctrine test
If you are evaluating any unmanned CBRN platform, ask one question first: show me the loop, and show me where a human can stop it. A vendor who answers with a flight demo has built a drone. A vendor who answers with a gate diagram has built a system.
Design analysis by UAM KoreaTech. Lattice-related integration statements describe our design goals and independent analysis; no third-party endorsement is implied. Specifications subject to verification.

Leave a Reply