LPI - Khan BMS Battlefield Management System
Working notes on LPI (Low Probability of Intercept): ew mesh context, design trade-offs, and where it fits in the Arban–Tumen hierarchy.
LPI is the kind of standard that looks finished on paper and turns out to be a set of unanswered design questions in practice. Anyone who tells you otherwise has not had to ship it.
Strip the marketing and LPI is exactly what the standard says: Low Probability of Intercept. Waveform property that minimizes the chance of detection by adversary signals intelligence. LPI waveforms keep emitted power spectral density low through wide bandwidth, short bursts, and rapid frequency agility, so that hostile intercept receivers cannot reliably detect the signal above the noise floor. LPI is paired with LPD (low probability of detection) and LPE (low probability of exploitation) to characterize stealth at the RF layer.
Khan BMS doesn't ship LPI 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.
LPI is anchored at the Arban — ten nodes under one tactical leader. Small enough to reason about by hand, large enough to absorb the loss of a node without re-planning. Authority for LPI is bounded at this tier; nothing the Arban does can poison its parent.
That is the unglamorous version of why Khan BMS exists: to make LPI a routine operating assumption instead of a research demo.