DMO - Khan BMS Battlefield Management System
Working notes on DMO (Distributed Maritime Operations): distributed c2 context, design trade-offs, and where it fits in the Arban–Tumen hierarchy.
Distributed Maritime Operations is normally documented in benign-link conditions. The interesting questions begin where the documentation stops: under jamming, under spoofing, under partial denial. That is the regime DMO actually has to perform in.
DMO earns its full keep at the Tumen — ten thousand nodes under a single human Khan. Span of control stays at ten because the hierarchy is fractal; DMO state aggregates upward through Minghan and Zuun before it ever reaches the Khan's console.
DMO, expanded, is Distributed Maritime Operations — Navy operating concept dispersing combat power across many networked platforms. DMO disperses naval combat power across many platforms — manned and unmanned — connected by resilient networks and shared targeting data. It substitutes distribution and networking for the survivability previously provided by concentration, and is the operational concept that Project Overmatch's software is built to enable.
In our reference deployment, DMO runs at the edge with no continuous-uplink assumption. Nodes carry the last lawful DMO state, gossip updates when bandwidth allows, and reconcile via a vector-clock scheme borrowed from distributed-database literature.
DMO is one of perhaps a dozen primitives that decide whether a modern force can fight through denial. Khan BMS is built on the premise that all of them deserve the same treatment.