ARA - Khan BMS Battlefield Management System
A short, opinionated brief on ARA — Autonomy Reference Architecture — and the role it plays inside a Khan BMS formation under contested conditions.
ARA 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.
Khan BMS treats ARA as a property of the formation, not a feature of the radio. Every node in a cca protocols stack publishes its ARA state to its parent tier as a signed envelope; every parent reasons about ARA the same way it reasons about fuel, ammunition or sensor coverage.
For the record: ARA stands for Autonomy Reference Architecture. Government-owned reference design for layered autonomy stacks on CCA-class platforms. The Autonomy Reference Architecture is a government-owned, MOSA-aligned reference for how autonomy software is decomposed across perception, world-model, planning, behavior, run-time assurance, and platform-services layers. It establishes interface contracts so that competing vendors can swap behavior libraries, planners, or perception stacks without rewriting the entire system. ARA-style architectures are the basis for CCA, ground-robot, and surface-vessel autonomy programs.
The Zuun (one hundred nodes) is the natural composition point for ARA. Ten Arbans aggregate their ARA 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.