Mission-Command Autonomy

Plain-language definition

Continue the mission locally without inventing a new mission.

The definition is intentionally bounded. It identifies the property or role under discussion without converting terminology into a claim of deployment, recognition, personhood, citizenship, sovereignty, or authority.

Technical definition

Within the K01 knowledge model, Mission-Command Autonomy is represented as a stable term object with code K01-TERM-168, canonical URL, claim status, topic owner, source links, related terms, last-reviewed date, research cutoff, and correction state. Relevant implementation components for the owning topic include mission intent; decentralized execution; assured timing and navigation; resilient communications; multi-agent coordination; model and sensor hardening; runtime assurance; authorization and abort controls.

Legal or policy use

Autonomous and semi-autonomous weapon systems remain subject to applicable domestic and international law, system approval, testing, rules of engagement, and human judgment requirements of the responsible authority.

When a statute, regulation, standard, or external institution uses a different definition, that source-specific meaning controls the analysis of that source. The project definition is not silently substituted into current law.

What the term implies

The term implies that the stated property should be evaluated using the evidence appropriate to multi-domain autonomy, resilient command and control, contested communications, swarm coordination, electronic warfare, cyber operations, and runtime assurance. It supports precise reference, comparison, data exchange, and correction across public prose and machine records.

What the term does not imply

It is not unrestricted self-direction or automatic target authority.

It also does not convert a valid signature, credential, database record, model hash, or website into factual truth or legal authority without additional evidence and a competent decision.

Commonly confused terms

• Runtime Assurance
• Adversarial Machine Learning
• Byzantine Agent
• Contested Communications

Confusion is resolved by asking which property is actually at issue: technical control, continuity, evidence, authority, legal recognition, operation, or normative status.

Operational test

1. Name the subject and purpose.
2. Identify the source definition and jurisdiction or technical context.
3. Collect evidence for the specific property.
4. Record currentness and limitations.
5. Route any governance, registry, assurance, or capital decision to the proper authority.

Related questions

• What is required before an autonomous warfare capability is fielded?
• How should Machine Intelligence defend against adversarial Machine Intelligence?

Sources

• DoD Directive 3000.09 — Autonomy in Weapon Systems — U.S. Department of Defense; DoDD 3000.09, January 25, 2023; Department of Defense Directive. Exact claim-support entries: 2. Revalidated 2026-08-15T20:00:00Z.
• The Establishment of Project Manager Cyber Warfare — U.S. Army Capability Program Executive Intelligence and Spectrum Warfare; Army release, August 3, 2026; Official first-party announcement. Exact claim-support entries: 2. Revalidated 2026-08-15T16:00:00Z.
• Cyber Warfare: The Best Offense Is a Powerful Defense — U.S. Army Acquisition Support Center; USAASC article, August 10, 2026; Official first-party article. Exact claim-support entries: 2. Revalidated 2026-08-15T16:00:00Z.

Stable term code: K01-TERM-168. Last reviewed 2026-08-16.