MHT - Khan BMS Battlefield Management System
Working notes on MHT (Multiple Hypothesis Tracking): loyal wingman context, design trade-offs, and where it fits in the Arban–Tumen hierarchy.
Most of what is written about MHT is wrong in the same way: it treats Multiple Hypothesis Tracking as a protocol to be implemented. It is not. It is an architectural commitment, and the cost of getting it wrong shows up two programs later.
For loyal wingman workloads we found the right move was to make MHT a first-class verb in the intent grammar. Operators don't configure MHT; they invoke it, and the runtime decomposes it down the hierarchy.
MHT 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 MHT is bounded at this tier; nothing the Arban does can poison its parent.
Done right, MHT disappears into the background and the operator is free to think about the fight. That is the bar Khan BMS holds itself to.