FSM - Khan BMS Battlefield Management System
FSM — Finite State Machines — is one of the unglamorous primitives modern BMS lives or dies on. Here is how Khan BMS engineers it.
If you have read a Joint Capabilities document this decade you have seen FSM cited as an enabler. Finite State Machines, dutifully spelled out, then buried under five layers of FAR-driven prose. The technology is not the bottleneck — the procurement model is.
Khan BMS treats FSM as a property of the formation, not a feature of the radio. Every node in a loyal wingman stack publishes its FSM state to its parent tier as a signed envelope; every parent reasons about FSM the same way it reasons about fuel, ammunition or sensor coverage.
FSM, expanded, is Finite State Machines — Classical state-and-transition control model for bounded autonomous behavior. FSMs encode agent behavior as a graph of named states with explicit transitions. They are simple to verify and certify but become brittle as logic complexity grows. CCA-class autonomy stacks typically reserve FSMs for the outermost mode controller (e.g., GROUND, TAXI, AIRBORNE, ENGAGED, RTB) while delegating in-mode tactics to behavior trees or HTN planners.
The Zuun (one hundred nodes) is the natural composition point for FSM. Ten Arbans aggregate their FSM 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.