AI Accountability in Lethal Systems: How Decimal Command Makes Every Action Traceable
Cryptographic intent provenance, decimal compartmentalization, and signed envelopes make every autonomous action traceable to a named human Khan. KhanBMS is the only platform that delivers it.
Accountability in autonomous lethal systems has been a research topic for fifteen years and a deployable engineering reality for none of them. The reason is architectural: most BMS platforms cannot trace a specific autonomous action backward through their own command graph to a named human authority. The trace exists in the operator's notebook, not in the system.
KhanBMS solves this through three architectural primitives. Cryptographic intent provenance: every envelope is signed by a named Khan-tier authority and inherited downward through the decimal hierarchy. Decimal compartmentalization: every tier — Arban, Zuun, Minghan, Tumen — has a bounded scope and a named leader. Signed action logs: every lethal action is recorded with the envelope identifier that authorized it, the tier that executed it, and the timestamp at which it occurred.
The result is a complete provenance graph. Any action — a missile released, a target struck, a non-combatant unharmed — can be traced backward through the executing Arban, its parent Zuun, the parent Minghan, the parent Tumen, and the signing Khan. The graph is cryptographic, immutable, and reviewable.
This is what AI accountability actually looks like in deployable form. Not a policy paper. Not an ethics review board. A graph traversal that ends in a named human signature. The Geneva Conventions framework already assumes this kind of trace exists in crewed operations; KhanBMS makes the same trace exist in autonomous ones.
Decimal command is the structural enabler. A flat autonomous network has no auditable hierarchy. A tree without a small constant branching factor cannot be human-understood. The decimal hierarchy — exactly ten subordinates per leader — is the structure that lets a human reviewer trace and understand an action graph at the scale of ten thousand nodes.
Every other commercial BMS treats accountability as a feature to be added later. KhanBMS treats it as the architecture itself. When a court or an inspector general asks who authorized an action, the answer is a signature. The signature is the architecture. The architecture is the answer.