What AutoWarCom Is — and What It Isn't Yet
Combatant commands fight wars. They don't buy equipment. INDOPACOM, EUCOM, CENTCOM, and SOCOM each organize warfighters and execute assigned missions. The military services — Army, Navy, Air Force, Marine Corps, Space Force — own acquisition: they run program executive offices (PEOs), manage development contracts, and receive appropriated funds through service-specific budget titles in the PPBE process.
AutoWarCom is being described differently. Hegseth's September 30 State of the Force address described the command as carrying "service-like authorities." Those three words are doing substantial analytical work. In the context of DoD organizational law, "service-like authorities" most plausibly means budget authority of its own — an appropriation line — and the associated program management infrastructure. That combination is how services buy things; it isn't how commands operate.
The only exception to this pattern is SOCOM. Established in 1987, SOCOM received acquisition authority under Section 167 of Title 10, enabling it to directly procure specialized equipment for special operations forces without routing everything through the Army, Navy, or Air Force. SOCOM maintains its own PEOs and manages its own programs. That structural independence enables faster movement on SOF-peculiar equipment — for common equipment, SOCOM remains subject to the same statutory acquisition requirements as the services — and it's the model AutoWarCom appears to be drawing from.
If AutoWarCom is to have genuinely equivalent authority, it needs Congressional action comparable to what created Section 167. Hegseth's announcement is a statement of intent. The enabling legislation has not been filed. That's the single most important procedural fact in the announcement.
The Acquisition Problem AutoWarCom Would Solve
To understand why an acquisition-capable AutoWarCom would matter, it helps to trace the specific dysfunction it's meant to address.
The services each develop autonomous platforms independently. Army autonomous ground vehicles, Navy unmanned surface vessels, Air Force collaborative combat aircraft, and Marine Corps UAS programs are acquired through separate service programs, often with incompatible data standards, different link architectures, and non-interoperable command interfaces. The result is a collection of capable platforms that can't readily operate as an integrated force. JADC2 — Joint All-Domain Command and Control — is the operational aspiration; the acquisition structure has worked against it.
The Defense Innovation Unit has partially addressed this through Other Transaction Authority (OTA), which bypasses much of the FAR procurement process. But OTA produces prototypes and limited-production contracts. Transitioning an OTA-originated program into a service program of record — the path to scale, sustainment funding, and eventual fleet-wide fielding — requires a service to adopt it. Services have institutional reasons to resist programs that didn't originate in their own requirements process. The "valley of death" between prototype and program of record has swallowed meaningful autonomous capability.
An acquisition-capable AutoWarCom changes this architecture directly. A command with its own program authority doesn't need a service to adopt a capability. It buys it, tests it, and fields it across the joint force. The interoperability standards are set by the command rather than negotiated across four services. The T&E baseline is common rather than service-specific.
That's the structural argument for service-like authorities. It's also the argument the services will resist.
Project Agincourt: Where the Architecture Is Being Written
Hegseth named Owen West — current Director of the Defense Innovation Unit — to lead Project Agincourt, the interim organization standing up AutoWarCom's operational concept alongside Navy SEAL Senior Chief Max Strasiser.
The choice of West is not incidental. DIU's OTA mechanism and SOCOM's acquisition model are the two existing organizational templates AutoWarCom could draw from. West knows both: he has spent his DIU tenure pushing autonomous systems contracts and working the transition problem between prototype and program of record. Pairing him with a special operations operator brings a user-community perspective into the conceptual design from the start.
Project Agincourt is not a placeholder. It will draft the concept of operations and the statutory proposal before Congressional hearings begin. The design choices made in the next six months — whether AutoWarCom holds its own appropriation, its own PEO, its own T&E authority — will almost certainly shape what Congress is asked to authorize. The window for companies to engage the concept while it is still being written is bounded.
A parallel commission, "Project Meridian," commissioned through MITRE Corporation by Pentagon CTO Emil Michael and co-directed by Elon Musk, Palmer Luckey (founder of Anduril Industries), and former House Speaker Newt Gingrich, is focused on the demand signal: what autonomous capabilities the future joint force actually needs, with findings due to the Pentagon by late January 2027. The co-directors' existing defense industry relationships — Luckey's in particular — make Meridian a political and commercial dynamics story as much as a technical one. Agincourt is the supply-side design; Meridian is the requirements analysis. Both are feeding into the statutory proposal.
What Can Fail
The SOCOM precedent is instructive but not uniformly encouraging. After Congress established SOCOM in 1987, the command spent much of its early years in jurisdictional conflict with the services over budget authority, program ownership, and the definition of what "special operations forces" actually needed. The arrangement stabilized — SOCOM now runs effective programs — but the friction was real and persisted into the 2000s.
AutoWarCom will encounter the same resistance in more concentrated form. Autonomous systems are not a niche capability; they are a central priority for all four services. Each service has ongoing programs, acquisition infrastructure, and institutional investment in its own autonomous systems path. An acquisition-capable AutoWarCom competes with all of them simultaneously.
Congressional authorization is the harder constraint. A new appropriation title requires authorization and appropriations legislation to move in sync. The October 1, 2027 target assumes action in the FY2027 or FY2028 NDAA cycle. The FY2027 NDAA is already complicated by the divergence between House and Senate positions on AI targeting and Directive 3000.09 review requirements. Adding an entirely new combatant command with acquisition authority to that debate introduces more negotiating surface, not less.
The credible alternative outcome: Congress authorizes AutoWarCom with coordination authorities only — joint requirements validation, interoperability standards, and shared T&E infrastructure — but no independent budget title or PEO structure. In that version, AutoWarCom sets the standards the services must meet; the services still buy. That outcome preserves the command's strategic framing and genuinely addresses interoperability without directly threatening service acquisition prerogatives. Whether it solves the transition problem is a harder question.
Evidence That Changes This Analysis
Three developments would materially alter the acquisition-authority conclusion:
If the statutory proposal describes coordination authority only. The language actually sent to Congress matters more than the speech. Watch for whether the proposal includes a new budget title (e.g., Title 10 appropriations authority), a PEO organizational structure, and a formal designation analogous to Section 167. Absence of those elements means the command's acquisition implications are limited.
If the FY2027 or FY2028 NDAA imposes substantial constraints on autonomous weapons acquisition. NSPM-11, signed June 5, 2026, directed a rapid update to Directive 3000.09 — the DoD policy governing autonomy in weapon systems — with apparent intent to reduce human-judgment requirements. If Congress codifies stricter oversight requirements than NSPM-11 envisions, those requirements would constrain what AutoWarCom is authorized to acquire regardless of its organizational authority.
If Project Agincourt recommends against independent acquisition authority. West's institutional background at DIU could support either recommendation. If the concept analysis concludes the better model is enhanced OTA authority — a DIU 2.0 with broader mandate — rather than a full acquisition command, the statutory proposal will reflect that. The interim organizational design is the signal to watch.
What This Means for Defense AI and Autonomy Companies Now
Regardless of which model AutoWarCom adopts, the announcement signals institutional commitment to treating autonomous warfare as an integrated domain rather than a set of parallel service programs. Several practical implications follow now, before the command structure is finalized.
Relationship positioning. Owen West is leading the organizational design. DIU relationships are the most direct access point. Project Agincourt's conceptual work is happening now, and industry engagement during this phase is typically possible and consequential. If your company has relevant technology — AI command interfaces, autonomy stacks, cross-domain communication architectures — this is the window in which the requirements are being written.
Standards and interoperability compliance. A command that sets joint requirements — even without direct acquisition authority — produces standards. Alignment with those standards becomes a de facto qualification threshold. AI data format choices, API contract designs, abstraction layer architectures made now will either map to AutoWarCom's eventual standards or require expensive rework. Treat the command's concept of operations documents as technical standards when they appear.
T&E positioning. The command will require a T&E framework for autonomous systems. Existing service T&E organizations have service-specific mandates; the joint T&E function for AutoWarCom programs is an open question. Companies with meaningful autonomous systems experience should be tracking the T&E discussion in Agincourt — both because they can contribute to it and because the resulting framework will define what verification and validation looks like for anything the command acquires.
The twelve months before AutoWarCom's statutory proposal reaches Congress are the highest-leverage period for shaping the acquisition architecture. What gets designed into the command's concept of operations now will be operationally consequential for years.
Spartan X's work on edge AI architectures, multi-platform command integration, and AI verification has been built around exactly the questions AutoWarCom will need to resolve: validating autonomous system behavior under degraded conditions, establishing interoperable data standards across heterogeneous platforms, and defining T&E criteria that hold in joint environments. That experience is directly relevant to what Project Agincourt needs as it drafts the command's concept of operations and the standards structure that will govern it.
Sources and further reading
- Hegseth "State of the Force" address, Marine Corps Base Quantico, September 30, 2026 — Defense Scoop (defensescoop.com/2026/09/30/hegseth-announces-autonomous-warfare-command/), Bloomberg (September 30, 2026)
- U.S. Special Operations Command acquisition authority: 10 U.S.C. § 167, Title 10 United States Code
- Defense Innovation Unit overview and OTA authority: diu.mil
- National Security Presidential Memorandum 11 (NSPM-11), June 5, 2026, directing update to DoD Directive 3000.09
- DoD Directive 3000.09 (Autonomy in Weapon Systems), most recent update January 2023 — esd.whs.mil
- FY2027 NDAA AI and autonomous weapons provisions — House Armed Services Committee markup; Senate Armed Services Committee markup (July 2026)
