// SYSTEM ARCHITECTURE

A fractal command system, scaled by ten.

KhanBMS is organized into five recursive tiers. Each tier commands exactly ten of the next. The result is a kill-web that scales linearly with hardware while keeping the operator's cognitive load constant.

TIER 01
ARBAN
×10
Arban — 'ten' in Mongolian

Edge tactical unit

The smallest indivisible combat unit. In KhanBMS this is a fireteam of unmanned assets: a CCA pair, a quadcopter swarm element, or a robotic ground squad. Each Arban runs the full decision stack on-board and is authoritative for its own kill-chain inside doctrine.

On-board autonomyMesh commsLocal sensor fusionROE enforcement
TIER 02
ZUUN
×100
Zuun — 'hundred'

Coordinated company

Ten Arbans synchronized into a single tactical effect. The Zuun layer composes formations dynamically: SEAD packages, screening lines, logistics convoys. Pilots and operators command at this tier.

Formation compositionCross-domain taskingPilot-in-the-loopEW coordination
TIER 03
MINGHAN
×1000
Minghan — 'thousand'

Battalion kill-web

Synchronizes battalion-scale unmanned operations across multiple Zuuns. Manages cross-cueing between sensor and shooter assets, deconflicts airspace, and allocates effectors against the joint target list.

Joint targetingAirspace deconflictionSensor-shooter cueingLogistics chain
TIER 04
TUMEN
×10000
Tumen — 'ten thousand'

Divisional formation

Operational-level command of an autonomous division. The Tumen integrates kinetic, EW, cyber and information effects into a campaign tempo. Built to fight through degraded comms via cached doctrinal intent.

Campaign tempoMulti-domain integrationDegraded-ops cacheStrategic reach
TIER 05
KHAN
×C2
Khan — the human commander

Command center

The only tier where intent originates. Khan operators set commander's intent, rules of engagement, and mission parameters. Everything below is bounded autonomy executing within those constraints. The human remains in command — not in the loop.

Intent authoringROE managementCross-Tumen orchestrationAfter-action review

Architected for the contested edge.

Read the doctrinal foundation behind the decimal command model.

Read the Doctrine