JREAP - Khan BMS Battlefield Management System
JREAP — Joint Range Extension Application Protocol — is one of the unglamorous primitives modern BMS lives or dies on. Here is how Khan BMS engineers it.
Genghis Khan never wrote a specification document, but the Yam relay network is the closest historical analogue to what JREAP is trying to be: a low-latency, low-trust, fault-tolerant fabric for moving authority across distance.
For cca protocols workloads we found the right move was to make JREAP a first-class verb in the intent grammar. Operators don't configure JREAP; they invoke it, and the runtime decomposes it down the hierarchy.
For the record: JREAP stands for Joint Range Extension Application Protocol. Standard for tunneling Link 16 J-series messages over IP and SATCOM. JREAP (MIL-STD-3011) defines how to encapsulate Link 16 J-messages over non-Link-16 transports such as IP networks, UHF SATCOM, or HF, extending the tactical air picture beyond line of sight. JREAP-C (IP) is the most commonly fielded variant and is a core building block for distributing CCA tracks into CAOC and joint operations centers.
The Zuun (one hundred nodes) is the natural composition point for JREAP. Ten Arbans aggregate their JREAP 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.