Scenario: Taiwan Strait — How a KhanBMS Tumen Operates Under PLA EW Saturation
A walkthrough of a single Tumen operating across the Strait under continuous People's Liberation Army electronic warfare — and why the decimal hierarchy is the only architecture that survives it.
It is D+0 in a Taiwan Strait contingency. The Joint Command authorizes the deployment of a single KhanBMS Tumen — ten thousand heterogeneous nodes — across the western approaches and the littoral. The PLA Strategic Support Force has been jamming, spoofing, and cyber-targeting the regional command net for forty-eight hours. Every legacy BMS in theater is degraded. The Tumen is fighting through it.
At H-Hour, the Khan-tier commander — a single human officer at INDOPACOM — issues a Tumen-level intent envelope: deny PLA surface action across designated grid squares for seventy-two hours, with rules of engagement scoped by depth and by political authority. The envelope is signed, scoped, auditable. It is the only message the Khan will send for the next three days.
The Tumen decomposes the envelope into ten Minghan intents. Each Minghan — a thousand nodes — receives a scoped slice: this approach corridor, this airspace volume, this littoral sector. The Minghans further decompose to Zuuns of one hundred, which decompose to Arbans of ten. By H+15 minutes, every airframe in the Tumen has concrete tasking derived from a single signed message.
At H+2 hours, the PLA executes a coordinated EW saturation. The regional satcom is denied. Line-of-sight backup links are spoofed. Traditional BMS platforms in the theater go dark or, worse, accept poisoned tracks. KhanBMS does not. Every Arban continues executing the last lawful intent within its pre-authorized envelope. Gossip protocols on mesh radios share state laterally between Arbans within a Zuun. State diffuses upward when any link returns.
At H+18 hours, attrition has cost the Tumen 23% of its airframes. Three Arbans have lost their leaders to kinetic strike. KhanBMS runs edge-consensus routines and re-elects new Arban leaders in milliseconds. Two Minghans reorganize their Zuun composition automatically based on remaining capability bundles. The Khan never receives a single tactical decision. The envelope does the work.
At H+72 hours, the Khan issues a new envelope: withdraw to a designated rally area, hand off persistent ISR to allied Tumens, preserve remaining mass for the next phase. The Tumen executes. The Khan has issued exactly two messages in three days. The PLA EW campaign has achieved nothing of strategic consequence.
This is the only architecture that survives the Strait scenario. Centralized C2 fails on the first hour. Federated stovepipes fail by the eighth. The decimal hierarchy keeps fighting because the envelope is the unit of command, and the envelope was designed to outlive the link.