Two Paths to the Same End State
The core problem is identical in both proposals: autonomous systems acquisition is fragmented across service program offices with different requirement cycles, evaluation criteria, and funding lines. Neither path disputes the problem. They disagree on who designs the new command.
The Senate Armed Services Committee path (Section 917) is a statutory one. It would give the President authority to establish the United States Robotic and Autonomous Systems Command — RASCOM — as a functional combatant command. The operative language in S. 4784 Sec. 917 is permissive: the President, through the Secretary of Defense, "may establish" RASCOM under section 161 of Title 10. The command exists only if the President exercises that authority. The SASC Committee reported the bill 18–9 on June 10, 2026 on a full-bill vote; only Sen. Kaine filed formal dissenting views with the committee, and those views did not address Sec. 917.
The administration path is executive. DRPM-UxS — the Direct Reporting Portfolio Manager for Unmanned Systems — was established in a June 29, 2026 memo posted July 1. That memo placed the Joint Interagency Task Force 401 (JIATF-401) and Defense Autonomous Warfare Group (DAWG) under DRPM-UxS, with both directors dual-hatted and their personnel and billets unchanged; the Defense Innovation Unit (DIU) serves as the industry interface. The September 30 Project Agincourt memo set the administration's end-state ambition: a full Autonomous Warfare Command (AUTOWARCOM) targeted for October 1, 2027 — itself a four-star functional combatant command the administration intends to seek legislation for. What the NDAA will determine is not statutory structure versus executive portfolio, but which statutory framework Congress provides for that command's design.
What Section 917 Actually Creates
The operative bill text, new 10 U.S.C. §167a, is permissive authority — not a study mandate, not a directive. The President may establish RASCOM, with a defined structure if that authority is exercised:
Authority scope. Section 167a(g) makes RASCOM the principal operational test-and-evaluation authority for all robotic and autonomous systems programs across the services. Section 167a(h) provides acquisition authority — delegable by the Secretary of Defense — covering limited-quantity experimental and prototyping contracts up to $20 million per award and purchases through pre-priced military-department contract vehicles. Section 167a(i) requires a separate major force program for RASCOM, the same mechanism that funds SOCOM through MFP-11. Section 167a(c) creates service component commands with dedicated career pathways.
Command relationships. Section 167a(d) establishes subordinate unified commands under each geographic combatant command's operational control, "funded and resourced through RASCOM." Sections 167a(d) and (e) address the C2 seam concern by limiting RASCOM's operational control within another combatant command's area unless forces are transferred or the Secretary directs otherwise.
The SASC committee report describes the provision as one that "would permit the President, through the Secretary of Defense, to establish" a RASCOM — consistent with the permissive bill text.
Why DRPM-UxS Is the Administration's Counter-Argument
The administration's argument is that DRPM-UxS is already building toward what RASCOM would authorize, without waiting for Congress to decide which design wins. Under the authorities the June 29 memo established, DRPM-UxS recommends investment allocations to the Deputy Secretary of Defense, operates Milestone Decision Authority for designated UxS acquisition programs (excluding current major defense acquisition programs and the Navy mUSV program), and runs competitive evaluations with operational forces at the edge. DRPM-UxS co-leads Owen West (CEO) and Max Strasiser (COO, a Navy SEAL senior chief) pair companies with operational forces, evaluate performance, and move resources toward what works.
There is an important limitation the June 29 memo is explicit about: DRPM-UxS control and tasking authority "does not extend to the operational employment of military forces." It is a portfolio authority, not an operational command.
The practical argument is speed. DRPM-UxS is running now. Across the services, operator-led evaluation cycles are active — the Army Applications Laboratory and 1st Cavalry Division are conducting autonomous systems experimentation at Fort Hood (Overwatch, October 13 through November 13) — illustrating why industry access to operational evaluation cycles before formal solicitations launch is the near-term channel question. Establishing RASCOM requires the President to exercise the §167a permissive authority, Defense Department implementation, and Senate confirmation of a nominated commander (Sec. 917 sets no grade; O-10 appointments require Senate consent under 10 U.S.C. §601).
The administration is not arguing it needs no legislation. The September 30 Agincourt memo explicitly directs DRPM-UxS to "collaborate directly with Congress to secure necessary legislation" — legislation for AUTOWARCOM's budget and acquisition authorities, for a command the memo describes as possessing "directed manpower, budget, acquisition authorities" and "dedicated military career pathways." The choice is not legislation versus no legislation. It is which statutory framework Congress writes: §167a's permissive RASCOM, or administration-designed AUTOWARCOM legislation.
The Case Against RASCOM — and Why It Matters
The Air & Space Forces Association's formal opposition, communicated in a June 30 letter publicized July 6, 2026, lays out the strongest counterargument. The AFA letter, signed by Chair Kathleen Ferguson and Lt. Gen. (Ret.) Burt Field, objects that RASCOM would be responsible for all functions and have authority to conduct operations through other combatant commands — including operational employment — across robotics and autonomous systems domains, a cross-domain reach the association argues would undermine coordination at the moment when autonomous system speed is the decisive variable.
Lt. Gen. (Ret.) David Deptula, dean of the Mitchell Institute, has written separately that domain integration is what makes autonomous systems effective — a command responsible for autonomous systems across air, maritime, and ground domains would need to synchronize with geographic combatant commands that hold operational theater authority, creating an inherent coordination seam. Section 167a(d) and (e) address this structurally by placing RASCOM's subordinate commands under geographic COCOM operational control and constraining RASCOM's own authority in those areas, but the synchronization responsibility remains.
This concern applies to DRPM-UxS as well: its June 29 memo establishes the same limitation, explicitly excluding operational employment. Neither the congressional nor executive path has fully resolved how the new command layer integrates with geographic commanders who actually fight.
An alternative path that both sides should consider — targeted acquisition authority reform within existing service channels, with DRPM-UxS coordination authority for investment prioritization — is what H.R. 8800 Sec. 834 and S. 4784 Sec. 921 already outline. Sec. 834 creates an Autonomy Integration Account and standards for portfolio acquisition executives who lead unmanned system portfolios. Sec. 921 requires the Navy and Air Force to submit plans to consolidate unmanned systems under single accountable officials and establishes a joint working group on robotic and autonomous systems. These provisions are live in both chambers and represent negotiating currency in any final compromise.
What the Post-Election Lame Duck Faces
The Senate has not passed either its own NDAA bill (S. 4784 cloture failed 50–46 on July 14) or H.R. 8800. Neither bill has completed the Senate floor. The expected path to a final FY2027 NDAA is not a conference committee but a compromise negotiated directly by Senate and House Armed Services Committee leaders — and that agreement may not close in this Congress. Breaking Defense reported on November 5 that analysts expect "both the NDAA and defense appropriations likely delayed until early 2027."
Three factors will shape what happens to Section 917:
Post-election power transition. Democrats take control of both chambers in January. Any RASCOM provision requiring Senate confirmation of a presidential nominee for a command the administration has not elected to establish faces structural friction. The administration's AUTOWARCOM path has executive branch momentum, but it too requires Senate confirmation of a nominated commander under 10 U.S.C. §601 and the new authorizing legislation it is itself seeking — giving the new Congress leverage over both designs. If the NDAA slips into the 120th Congress, Section 917 and any AUTOWARCOM authorization provision are both subject to new Armed Services committee leadership.
CR deadline pressure. The continuing resolution expires December 11 (per Breaking Defense, November 5). NDAA negotiations compete for lame-duck floor time with appropriations. If Section 917 or AUTOWARCOM authorization legislation becomes a floor-time argument rather than a committee agreement, it may be traded out in favor of provisions with broader cross-chamber consensus.
Reconciliation is a separate and uncertain track. The FY2027 budget request includes $54.0 billion for autonomous and remotely operated systems, of which $39.2 billion is the mandatory Drone Dominance request tied to reconciliation and approximately $14.8 billion is discretionary. That reconciliation bill is not moving: the House passed a budget resolution carrying $60 billion for defense, but Senate Majority Leader Thune has declined to bring it to a vote, and Byron Callan of Capital Alpha put reconciliation passage odds at approximately 10 percent. The discretionary autonomy appropriation is a separate decision from reconciliation. Neither RASCOM nor DRPM-UxS changes the acquisition calculus if the underlying funding is not appropriated.
The practical outcome range: Section 917 survives as written (permissive §167a authority), gets narrowed to a study-and-report mandate, is replaced by an AUTOWARCOM authorization, or rolls into 2027 with a new Congress. Each outcome has different channel implications for industry.
What to Watch
Three signals in the next 60 days will indicate how autonomous command authority is settling:
- Whether Armed Services Committee leaders reach a framework agreement. A §167a permissive grant, a study mandate, an AUTOWARCOM authorization, or omission of a command provision are distinct outcomes with different channel implications. Track when committee staff announce or leak a compromise framework — that is when the fate of Section 917 in the final bill becomes legible. If the NDAA slips into 2027, the question moves to the new Armed Services leadership in the 120th Congress.
- The October 30 DRPM-UxS POAM. The Project Agincourt memo directed a plan of action and milestones due October 30 describing how AUTOWARCOM would relate to the services and what forces each would provide. That document was not publicly released as of this writing. Its release — or absence — will signal whether the administration is deferring AUTOWARCOM architecture to Congress or moving ahead with executive implementation.
- December 11 CR and FY2027 discretionary appropriations. How Congress handles the continuing resolution and the eventual appropriations bill determines whether the discretionary portion of the $54.0 billion autonomy request is funded. The mandatory reconciliation package is a separate and uncertain track. Do not conflate the two when modeling program timelines.
For defense companies, the near-term procurement channel question — service PAE, DRPM-UxS evaluation, or future RASCOM/AUTOWARCOM procurement vehicle — is not resolved by either existing document. What is resolved: operator-led evaluation is the stated standard for both paths. Getting systems into exercises like Overwatch before formal solicitations are released remains the most defensible near-term position regardless of how the command authority question settles.
Sources and further reading
- S. 4784, FY2027 NDAA as reported, including Sec. 917 (new 10 U.S.C. 167a), Sec. 921, govinfo.gov
- U.S. Senate Armed Services Committee, S. Rept. 119-127, govinfo.gov, June 2026
- H.R. 8800, FY2027 NDAA as passed by the House, including Sec. 834, govinfo.gov
- Air & Space Forces Association, AFA Opposes Proposed Robotic and Autonomous Command, June 30, 2026
- Congressional Research Service, FY2027 NDAA: Status of Legislative Activity (IN12704), 2026
- U.S. Department of War, Establishment of DRPM-UxS, June 29, 2026
- Secretary of War Pete Hegseth, Project Agincourt: Pathway to the Autonomous Warfare Command, September 30, 2026
- U.S. Department of War, CENTCOM Benefits from Project Agincourt Drone Dominance Efforts, 2026
- U.S. Department of War, FY2027 Budget Request Overview Book, comptroller.war.gov
- U.S. Department of War, Secretary Hegseth announces six major initiatives at Quantico speech, Release 4615424
- Inside Unmanned Systems, The Pentagon's New Drone Czar, August 2026
Spartan X works at the intersection of AI reasoning and autonomous system integration — specifically the C2 architecture problems that neither RASCOM nor AUTOWARCOM have fully specified in implementation. BRIC edge C3 addresses the forward-deployed C3 layer where autonomous system outputs converge — integrating sensor data from UAS and UGV platforms in DDIL environments, providing edge AI inference and tactical C3 at the kill chain. Archeon C4 addresses command and control for autonomous maritime platforms: a shared operating picture and distributed command layer for unmanned surface and undersea vehicles operating in DDIL conditions. The competitive evaluation standard DRPM-UxS is now making the norm — systems assessed against operator performance in realistic scenarios — is exactly the environment that tests those integration questions.
