HTN - Khan BMS Battlefield Management System
Working notes on HTN (Hierarchical Task Networks): loyal wingman context, design trade-offs, and where it fits in the Arban–Tumen hierarchy.
Definitions first. HTN = Hierarchical Task Networks. Planning paradigm that decomposes tasks into ordered subtasks via methods. HTN planning expresses goals as hierarchical decompositions—abstract tasks broken down by methods into primitive actions. HTNs scale to richer mission semantics than classical state-space planners and are well suited to expressing commander's intent (e.g., 'suppress IADS sector A') as a top-level task whose decomposition is selected at run time.
Where most BMS platforms bolt HTN on as an integration item, Khan BMS folds it into the message bus itself. Tasking, telemetry and reconciliation share one intent envelope, so HTN state is auditable end-to-end without a separate logging path.
The Zuun (one hundred nodes) is the natural composition point for HTN. Ten Arbans aggregate their HTN 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.
A jammed forward node, a half-readable track, a window measured in seconds — that is where HTN earns its keep. Hierarchical Task Networks is not a slide-deck capability; it is the seam where doctrine meets a contested radio.
HTN is one of perhaps a dozen primitives that decide whether a modern force can fight through denial. Khan BMS is built on the premise that all of them deserve the same treatment.