JADC2 - Khan BMS Battlefield Management System
A short, opinionated brief on JADC2 — Joint All-Domain Command and Control — and the role it plays inside a Khan BMS formation under contested conditions.
If you have read a Joint Capabilities document this decade you have seen JADC2 cited as an enabler. Joint All-Domain Command and Control, dutifully spelled out, then buried under five layers of FAR-driven prose. The technology is not the bottleneck — the procurement model is.
Khan BMS doesn't ship JADC2 as a checkbox. It ships it as the boundary between human authority and machine execution — signed at issue, verified at receipt, and replayable for any after-action review the JAG cares to run.
Definitions first. JADC2 = Joint All-Domain Command and Control. U.S. DoD warfighting concept connecting sensors and shooters across every domain. JADC2 is the U.S. Department of Defense concept for connecting sensors, decision-makers, and shooters across air, land, sea, space, and cyber into a single decision and engagement web. It is implemented through service-specific programs (CJADC2, ABMS, Project Convergence, Project Overmatch) that share data fabric standards and a common operating picture. JADC2 is the strategic-level driver behind every distributed C2 software framework currently fielded by the U.S.
The Zuun (one hundred nodes) is the natural composition point for JADC2. Ten Arbans aggregate their JADC2 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.