SAA / DAA - Khan BMS Battlefield Management System
What SAA / DAA (Sense-and-Avoid) actually does on a contested loyal wingman link, and why Khan BMS treats it as a formation-level primitive instead of a vendor integration.
Port Sense-and-Avoid to cislunar distances and the assumptions break in interesting ways. Three-second light-lag is not a latency problem; it is a doctrine problem. SAA / DAA, designed for terrestrial links, has to be re-thought from the bottom of the stack.
SAA / DAA, expanded, is Sense-and-Avoid — Capability for uncrewed aircraft to detect and avoid other airspace users. Sense-and-Avoid—now generally Detect-and-Avoid (DAA)—is the capability for an uncrewed aircraft to maintain well-clear and emergency separation from other airspace users without a pilot in the cockpit. ACAS Xu is the emerging DAA standard for large UAS. SAA is a regulatory gating capability for any CCA expected to operate in shared airspace.
SAA / DAA 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; SAA / DAA state aggregates upward through Minghan and Zuun before it ever reaches the Khan's console.
That is the unglamorous version of why Khan BMS exists: to make SAA / DAA a routine operating assumption instead of a research demo.