AUTOWARCOM and the Warfighting Acquisition Model: What Program Offices Need to Know

What AUTOWARCOM Is — and Isn't Yet

AUTOWARCOM as announced would lead the joint force in unmanned and autonomous warfare — a designated functional combatant command with its own directed manpower, budget, and acquisition authorities. Hegseth described it in the State of the Force address as a command with "service-like authorities," with dedicated career fields for officers and enlisted personnel working autonomous and robotic systems.

The command's mandate spans drones and autonomous systems, and what Hegseth called at the October 14, 2026 Association of the United States Army meeting "domain synthesis" from space to subsea. The design intent is a joint integrator with authority to scale what works rather than a program office managing a single platform.

It does not exist yet. The September 30 memorandum, titled "Project Agincourt — Pathway to the Autonomous Warfare Command," creates an interim effort and directs DRPM-UxS to work with Congress to secure necessary legislation, with October 1, 2027 as the target. The memo also provides that initial work will proceed immediately under existing authorities. Congressional action is required. The Senate Armed Services Committee's FY2027 NDAA markup includes Section 917, a provision that would permit — not require — the President to establish the Robotic and Autonomous Systems Command. That bill (S. 4784) stalled on the Senate floor after a failed cloture vote in July 2026; the House passed its own FY2027 NDAA (H.R. 8800) in July 216-212. No FY2027 NDAA had been enacted as of late October 2026.

The organizational groundwork began earlier. On June 29, 2026, the Direct Reporting Portfolio Manager for Unmanned Systems (DRPM-UxS) was designated as the single joint integrator for unmanned and autonomous programs. The June 29 memo placed JIATF-401 and the Defense Autonomous Warfare Group (DAWG) under DRPM-UxS direction, and established DIU as the primary industry engagement interface. By October, that structure was evolving: at the AUSA panel, Derrick Anderson, Assistant Secretary of War for Special Operations and Low-Intensity Conflict, described DAWG moving into a SOCOM-led autonomous warfare task force in direct support of AUTOWARCOM; Hegseth separately described DAWG as merging into Project Agincourt. Hegseth appointed Owen West — then DIU director — and Navy SEAL Senior Chief Max Strasiser, described in the DoW release as the first enlisted SEAL to graduate from Navy Test Pilot School, to lead DRPM-UxS in a CEO-COO structure and direct Project Agincourt.

The Warfighting Acquisition Model

The most significant element of Hegseth's September 30 address for acquisition professionals is not the command structure — it is the "Warfighting Acquisition" construct that Project Agincourt will pilot.

Hegseth described it in his State of the Force address: "This model fuses operators with entrepreneurs in rapid adaptation cycles, while distributing decisions and dollars closer to frontline units and the combatant commands. Realistic training exercises, and when possible, the crucible of combat, will be used to compress innovation timelines and scale what works."

One reference point discussed at the October 14 AUSA panel was SOCOM's procurement experience, described by Derrick Anderson, Assistant Secretary of War for Special Operations and Low-Intensity Conflict. Anderson described defining eight to nine TSOC problem sets, giving industry 30 days to submit white papers, then convening a pitch with "warfighters in the room, acquisition officials in the room, the TSOCs in the room" — and awarding a contract on the same day. He characterized it as compressing an 18-to-24-month cycle to roughly two months, then added the caveat: "SOCOM is small, so we're iterating on smaller problems." What AUTOWARCOM proposes is testing whether a structurally similar approach can work at joint-force scale.

West and Strasiser's open letter to industry made the institutional ambition explicit: "Autowarcom will institutionalize a mission-based system whose main product is adaptation, building a next-generation development model for sustained American military advantage." The letter also signaled cost discipline, with West and Strasiser stating that the "power of the purse" demands strict stewardship, and that every auditable dollar spent should reduce cost or risk.

That framing has a concrete implication for vendors and program offices alike. Companies that can supply high-volume, production-ready capability with a defensible unit cost structure fit the declared model better than those whose value proposition is a prototype plus a development roadmap. Hegseth's reference to the Drone Dominance program — credited in the DoW release with delivering "thousands of robotic systems to the Middle East in support of Operation Epic Fury" — gives the clearest signal of what the acquisition posture is rewarding.

The Army's Early Response: FASCOM

The Army moved the fastest to comply. Acting Secretary Adam Telle signed a memorandum on October 1, 2026 directing the establishment of the U.S. Army Futures and Autonomous Systems Command (FASCOM). On October 13, Gen. Christopher LaNeve, Vice Chief of Staff and Acting Chief of Staff of the Army, formally redesignated Futures and Concepts Command as FASCOM. In Telle's words at the AUSA panel, FASCOM "feeds up into Autowarcom" when the joint command activates.

Telle's directive is notable for its specificity. It calls for:

Integration of autonomous capabilities into at least six formation areas: aviation, armor, fires, sustainment, engineer, and training formations
Designation of a Portfolio Acquisition Executive for Autonomy
Prioritization of acquisition and fielding of autonomous fires, combat vehicles, watercraft resupply, breaching, reconnaissance, and surveillance and target acquisition capabilities, and collaborative crewed-uncrewed teaming, no later than fiscal year 2028

That no-later-than-FY2028 fielding priority is an independent acquisition anchor. It is not conditioned on AUTOWARCOM's Congressional authorization — the Army is building the formation and acquisition structure now, with AUTOWARCOM as the eventual joint authority above it.

At a panel on October 13, Lt. Gen. Mac McCurry described FASCOM's focus in terms of four task types: dull, dirty, dangerous, and "decisive" — meaning systems that accelerate decision advantage, per National Defense Magazine's coverage of the event. Federal News Network reporting from the same panel indicated McCurry's stated priority is working through how to adopt technology quickly without getting bogged down in formal incorporation processes, with autonomous decision-support among the areas highlighted.

Where This Can Fail

Hegseth framed his expectation of resistance at Quantico with historical precedents: Goldwater-Nichols, the creation of SOCOM, the MRAP fight under Secretary Gates, and the establishment of Space Force — all changes that, in his telling, "always met resistance" but succeeded once the commitment was clear. He invoked SOCOM, the MRAP fight and Goldwater-Nichols again at AUSA. Three of those precedents were organizational reforms; MRAP was an urgent acquisition push, where Gates had to fight his own bureaucracy to fast-track a vehicle program. AUTOWARCOM attempts both at once — organizational redesign and a new acquisition model — which is a harder combination to execute.

The structural risks are four.

Congressional authorization is the first gate. Section 917 of the Senate FY2027 NDAA would permit the command, but the Senate bill stalled on the floor and no NDAA has been enacted. Until an NDAA or other statute authorizes the command, Agincourt proceeds under existing authorities, per the September 30 memo itself.

Acquisition authority fragmentation is the second. SOCOM's rapid acquisition cycle works because SOCOM is a single command with a defined mission set and an established vendor ecosystem. A joint command spanning Army, Navy, Air Force, and Marine Corps components — each with existing program executive offices and active procurement programs — creates coordination overhead that Warfighting Acquisition is explicitly designed to eliminate but has not yet faced at that scale. Telle's memo simultaneously creates a Portfolio Acquisition Executive for Autonomy whose relationship to existing Army PEOs is not publicly detailed.

Service and SOCOM alignment is the third. The Army has named FASCOM as its link to AUTOWARCOM; SOCOM has described a supporting autonomous warfare task force; other services have not yet announced equivalent structures in the sources reviewed. Hegseth stated at AUSA that "these services are not fighting us on that concept; they believe in it," but allocating acquisition budget and senior officer billets to a new command's component is a different decision from expressing conceptual alignment — and one made in a budget cycle that has not closed.

Program-of-record integration is the fourth. Autonomous programs already underway — Army UAS procurement, Navy unmanned maritime systems, Air Force Collaborative Combat Aircraft development — are running under existing PEOs with established budget lines. What happens to programs whose qualification timelines don't fit the no-later-than-FY2028 fielding priority is not publicly detailed in the documents reviewed.

What Acquisition Professionals and Industry Should Watch

The near-term signal is the 30-day plan of action Hegseth's September 30 memo required of DRPM-UxS — covering command relationships, resources, required authorities, and initial operating capability milestones — due approximately October 30 for Hegseth's approval. The memo does not commit to releasing it publicly, but any elements that surface will define where authority sits between Project Agincourt and existing PEOs.

The decision framework for program offices managing current autonomous or AI-enabled programs:

Does this program's unit cost and production timeline fit the Warfighting Acquisition model? Programs that require multi-year qualification before fielding will not fit naturally into the iteration cadence AUTOWARCOM is designed around.
Is there a credible path to the six formation areas Telle's memo identifies by FY2028? Programs demonstrating readiness across multiple formation types gain budget visibility and priority under the current Army posture.
What evidence would the combatant command use to scale or cut this program? West and Strasiser's letter defines adaptation as the central product. Programs without a feedback mechanism from operational use to capability development are structurally misaligned with what AUTOWARCOM's acquisition model rewards.

For industry, the alignment question is more direct: production capacity and unit cost matter more under this model than design sophistication. A vendor whose supply chain can deliver at the volume the Drone Dominance program demonstrated is better positioned than a vendor with a technically superior prototype on a 36-month production ramp.

Programs dependent on the traditional program-of-record pathway will still exist in the FY2028 budget environment — exquisite platforms with long development timelines serve requirements that attritable systems cannot fulfill. But funding priority, oversight visibility, and career incentives for acquisition officers are shifting toward programs that fit the iteration model. That is the core decision AUTOWARCOM's architecture forces on every existing program office working in the autonomous systems space.

Programs moving at Project Agincourt's tempo — iterating through training exercises and adapting from field results — will also need AI assurance processes that fit inside the iteration cycle rather than acting as sequential qualification gates. Arbiter, Spartan X's AI assurance platform in development, is designed to address exactly this problem: embedding assurance into the development loop rather than holding it as a final gate, so programs can accelerate without accumulating unexamined risk in their AI decision chains.

What AUTOWARCOM Is — and Isn't Yet

The Warfighting Acquisition Model

The Army's Early Response: FASCOM

Where This Can Fail

What Acquisition Professionals and Industry Should Watch

Sources and further reading

More from Signal

Warfighting Acquisition: What Project Agincourt's Open Letter Demands from Defense Companies

AutoWarCom and the Acquisition Question: What 'Service-Like Authorities' Actually Mean for Autonomous Systems

Army TITAN: The Integration and Support Behind an AI-Enabled Ground Station

Ready to Solve Hard Problems?