Popular culture portrays autonomy as science fiction, but real military autonomy is layered, incremental, and mission-dependent, according to Randy Yamada and Tom Schaefer of War on the Rocks. Ukraine’s semi-autonomous drone swarm “Operation Spiderweb” demonstrates how autonomy enhances coordination without removing humans from the loop. For the Pentagon to build a more autonomous, commercially aligned force, it must fix the current confusion over what “autonomy” means, as services and vendors use the term inconsistently.
Clear definitions, standardized technical layers, and interoperable architectures are essential—especially for joint scenarios like defending Taiwan, where incompatible systems could have dangerous consequences. Establishing common standards would guide acquisition, accelerate innovation, and unify fragmented approaches, much as the adoption of USB did for computing.
Equally important is building operator trust through education and early integration. Without Pentagon leadership in defining autonomy and standardizing communication layers, marketing hype will fill the gap—risking confusion that could translate into battlefield failure. They write:
Popular culture often distorts autonomy into science fiction caricatures. This framing obscures the real challenges and opportunities facing the U.S. military: autonomy as a layered, incremental capability, always shaped by mission context.
Ukraine’s “Operation Spiderweb,” in which over a hundred drones conducted a coordinated, semi-autonomous attack, illustrates this reality. Operators tasked and launched the systems, but autonomy enabled distributed navigation, deconfliction, and timing. It wasn’t a leap to science fiction. It was a practical demonstration of how autonomy can multiply effects and impose asymmetric costs.
For the Pentagon to realize a commercial-first and more autonomous force, it must overcome a lack of clarity around how the defense industrial base defines autonomy. […]
Within the defense sector, there are numerous organizations and partners, each with its own portfolio of platforms, that the Pentagon would ideally want to communicate with. Interoperability, or the ability for systems to exchange and make use of information, is incredibly important for autonomous systems to work together successfully and achieve common goals. But the systems will not be able to effectively communicate without a shared taxonomy and common language. […]
It can be challenging to navigate the ambiguity between autonomy layers when integrating across partners, something that is currently taking up considerable human effort.
Government reference architectures are designed to solve this problem. These are standardized frameworks created by government agencies to guide the design, implementation, and integration of systems. For example, the Agile Mission Systems Government Reference Architecture was an attempt to enable quick interoperability by integrating payloads. […]
The Pentagon should move quickly to establish a standard layer for autonomy messaging and tasking, much as transport protocols unified the internet, or risk incoherence in future conflict. The fog of marketing could thicken into a fog of war, and that is a risk the United States cannot afford.
Read more here.
