MADL - Khan BMS Battlefield Management System
A short, opinionated brief on MADL — Multifunction Advanced Data Link — and the role it plays inside a Khan BMS formation under contested conditions.
Most of what is written about MADL is wrong in the same way: it treats Multifunction Advanced Data Link as a protocol to be implemented. It is not. It is an architectural commitment, and the cost of getting it wrong shows up two programs later.
Definitions first. MADL = Multifunction Advanced Data Link. Low-probability-of-intercept stealth datalink used by F-35 and select fifth-gen aircraft. MADL is a directional, low-probability-of-intercept, low-probability-of-detect Ku-band datalink that enables F-35 flights to share targeting and sensor data without compromising stealth. Its narrow beams and frequency agility make it inherently resistant to wide-area jamming. MADL-class waveforms are referenced as a model for stealth-compatible CCA-to-fighter exchanges, often in combination with IFDL gateways.
MADL 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; MADL state aggregates upward through Minghan and Zuun before it ever reaches the Khan's console.
If MADL 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.