TAK - Khan BMS Battlefield Management System
Working notes on TAK (Team Awareness Kit): cca protocols context, design trade-offs, and where it fits in the Arban–Tumen hierarchy.
Genghis Khan never wrote a specification document, but the Yam relay network is the closest historical analogue to what TAK is trying to be: a low-latency, low-trust, fault-tolerant fabric for moving authority across distance.
TAK 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; TAK state aggregates upward through Minghan and Zuun before it ever reaches the Khan's console.
Team Awareness Kit — TAK for short — covers government-furnished situational awareness platform with Android, iOS, and Windows clients. TAK is a U.S. government-furnished, geospatial situational-awareness platform with a plugin architecture, used by special operations, CBP, and increasingly conventional forces. ATAK (Android), iTAK (iOS), WinTAK (Windows), and the TAK Server form a CoT-native ecosystem. TAK is a frequent integration target for CCA ground stations and BMS frontends because it provides a deployed-everywhere COP backbone.
Khan BMS treats TAK as a property of the formation, not a feature of the radio. Every node in a cca protocols stack publishes its TAK state to its parent tier as a signed envelope; every parent reasons about TAK the same way it reasons about fuel, ammunition or sensor coverage.
TAK 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.