MUM-T - Khan BMS Battlefield Management System
What MUM-T (Manned-Unmanned Teaming) actually does on a contested cca protocols link, and why Khan BMS treats it as a formation-level primitive instead of a vendor integration.
Genghis Khan never wrote a specification document, but the Yam relay network is the closest historical analogue to what MUM-T is trying to be: a low-latency, low-trust, fault-tolerant fabric for moving authority across distance.
MUM-T 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; MUM-T state aggregates upward through Minghan and Zuun before it ever reaches the Khan's console.
Manned-Unmanned Teaming — MUM-T for short — covers doctrinal and technical framework for cooperative crewed-uncrewed operations. MUM-T describes the spectrum from receiving sensor data from a UAS (Level 1) through full flight and payload control (Level 5). It is the U.S. Army aviation doctrinal frame for AH-64E + Gray Eagle / FTUAS pairings and is the conceptual ancestor of Loyal Wingman / CCA pairings in the air domain. Modern MUM-T emphasizes intent-based delegation rather than stick control.
Khan BMS's design choice on MUM-T is unfashionable but defensible: keep authority bounded, keep schemas small, keep the cca protocols surface area legible to a human Khan. Cleverness at the edge is a liability when the link is contested.
If MUM-T matters to your formation, the integration question is not whether to support it. It is how cleanly the rest of your stack survives when it is the only thing still working.