AUTOWARCOM Is Heading for a Command-and-Control Collision

RealClearDefense | Michael Carvelli

Secretary Pete Hegseth announced on September 30 the creation of the Autonomous Warfare Command with an October 1, 2027 establishment date under the Project Agincourt memorandum. This four-star functional combatant command aims to integrate service-provided autonomous systems, define joint operational needs, and accelerate fielding across defense branches. Operational pressures in Ukraine, the Middle East under Operation Epic Fury, and Nagorno-Karabakh demonstrate rapid tactical shifts driven by cheap drones.

Structural parallels from U.S. Special Operations Command, U.S. Cyber Command, and Army Futures Command illustrate institutional friction when operational authorities overlap with service acquisition functions. Unclear boundaries risk reproducing existing bureaucratic bottlenecks. The simultaneous establishment of the U.S. Army's Futures and Autonomous Systems Command creates immediate friction over procurement, testing standards, and program objective memorandum preparation. Without explicit congressional mandates defining funding streams and operational decision rights, AUTOWARCOM will struggle to maintain rapid technological adaptation across the joint force.

Comment

Establishing a functional combatant command for autonomous systems introduces structural friction between operational requirements and service-level procurement prerogatives. When U.S. Cyber Command was created, its lack of direct Major Force Program funding initialised years of budget wrangling with the military departments over equipment standardisation. Without statutory Title 10 authority over research and acquisition streams, AUTOWARCOM risks becoming an advisory body dependent on service branches for hardware delivery.

This institutional divide produces immediate operational vulnerabilities across multi-domain tactical nodes. Service branches will likely prioritise proprietary architectures to protect internal budget shares, impeding cross-domain data link integration during exercises like Arcane Thunder 26. Consequently, battlefield commanders operating under U.S. European Command will face fragmented autonomous networks rather than unified command authority.

Strategic Question for Discussion

If AUTOWARCOM lacks Major Force Program budget authority similar to early U.S. Cyber Command, will service branches prioritise joint autonomous integration, or will proprietary platforms dominate theater operations?

The historical pattern from Cyber Command suggests service branches will retain control over primary procurement budgets, favouring service-specific requirements over joint compatibility. My assessment is that without direct statutory acquisition power, AUTOWARCOM will struggle to enforce standardised data architecture across component forces. This dynamic leaves theater commands reliant on ad-hoc patch solutions during joint exercises like Arcane Thunder 26.

Share your assessment in the comments below.

To read in details click here