MOSA - Khan BMS Battlefield Management System
MOSA — Modular Open Systems Approach — is one of the unglamorous primitives modern BMS lives or dies on. Here is how Khan BMS engineers it.
Eight hundred years before MOSA had a NATO STANAG, the Mongol post-rider system was already solving the underlying problem: deliver intent across a contested span faster than the enemy can react. The vocabulary changed; the geometry did not.
Khan BMS's design choice on MOSA 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.
Modular Open Systems Approach — MOSA for short — covers u.S. DoD acquisition mandate requiring open architectures and standardized, replaceable modules. MOSA is a U.S. Department of Defense business and technical strategy that requires major weapon systems to be designed with modular boundaries and open, consensus-based interfaces so that subsystems can be competed, refreshed, and replaced without redesigning the host platform. It is codified in 10 U.S.C. §4401 and DoDI 5000.UA, and is the umbrella doctrine that pulls in lower-level technical standards such as Open Mission Systems, SOSA, FACE, and CMOSS. For Collaborative Combat Aircraft programs, MOSA compliance is generally treated as a precondition for inclusion of third-party autonomy stacks, payloads, and datalinks.
The Zuun (one hundred nodes) is the natural composition point for MOSA. Ten Arbans aggregate their MOSA state into one Zuun-level picture; one Zuun commander supervises ten subordinates, never a hundred individual feeds. The cognitive-load math is the entire point.