DDS - Khan BMS Battlefield Management System
Working notes on DDS (Data Distribution Service): cca protocols context, design trade-offs, and where it fits in the Arban–Tumen hierarchy.
Data Distribution Service — DDS for short — covers oMG real-time publish-subscribe middleware standard widely used in defense. DDS is an Object Management Group standard for data-centric, decentralized publish-subscribe communication with rich Quality of Service controls (deadline, durability, reliability, ownership). It is the messaging substrate used by many naval combat systems, OMS implementations, and autonomy stacks because it scales without a central broker. DDS Security adds authentication, access control, and encryption suitable for cross-domain mission systems.
DDS is the kind of standard that looks finished on paper and turns out to be a set of unanswered design questions in practice. Anyone who tells you otherwise has not had to ship it.
At the Minghan tier — one thousand nodes — DDS stops being a tactical convenience and becomes an operational capability. A Minghan commander issues DDS-shaped intent and lets the ten subordinate Zuuns decompose it; the human never sees a thousand individual streams.
For cca protocols workloads we found the right move was to make DDS a first-class verb in the intent grammar. Operators don't configure DDS; they invoke it, and the runtime decomposes it down the hierarchy.
Done right, DDS disappears into the background and the operator is free to think about the fight. That is the bar Khan BMS holds itself to.