The JADC2 Vision and Its Autonomous Gap
Joint All-Domain Command and Control (JADC2) represents the Department of Defense's vision for connecting sensors, shooters, and decision-makers across all domains — air, land, sea, space, and cyber — into a unified command and control fabric. The objective is to compress the kill chain, enable faster decision-making, and achieve information advantage over adversaries who operate with centralized, hierarchical command structures.
Each service has its own contribution to JADC2: the Army's Project Convergence, the Air Force's Advanced Battle Management System (ABMS), and the Navy's Project Overmatch. These programs are making progress on the fundamental technical challenges of data transport, message standardization, and cross-domain connectivity. But there is a significant gap in the JADC2 vision that receives insufficient attention: how autonomous platforms participate.
The current JADC2 architecture implicitly assumes that the entities producing and consuming information are human operators and manned platforms. The message formats, decision timelines, and authority structures are designed for humans in the loop. Autonomous platforms — unmanned aerial systems, unmanned surface vessels, autonomous ground vehicles, and AI-driven decision aids — do not fit cleanly into this paradigm. They produce data at machine speed, consume it differently than human operators, and require different authority frameworks for action.
Interoperability at Machine Speed
The interoperability challenge in JADC2 is already significant for manned platforms operating different data links, message standards, and communication protocols. Autonomous platforms amplify this challenge by orders of magnitude because they generate and require data at volumes and speeds that human-oriented interfaces cannot accommodate.
An autonomous ISR platform conducting surveillance of a maritime area may classify and report dozens of contacts per hour, each with associated metadata — radar cross-section, electromagnetic emissions, behavioral analysis, confidence levels, and cross-referenced intelligence. Pushing this data through a system designed for human-generated spot reports and chat messages creates a bottleneck that negates the speed advantage autonomy is supposed to provide.
Machine-to-machine data exchange standards must be a first-class element of the JADC2 architecture, not an afterthought. This means standardized APIs for autonomous platform reporting, common data models for sensor products that enable automated fusion, and message queuing architectures that can handle the burst traffic patterns characteristic of autonomous sensor operations. The intelligence products from autonomous platforms must be consumable by both human analysts and AI-driven decision aids without manual reformatting.
Trust and Authority Frameworks
Beyond data interoperability, autonomous platform integration into JADC2 raises fundamental questions about decision authority. When an autonomous underwater vehicle detects a submarine contact and classifies it as hostile with 87% confidence, what actions is it authorized to take? Can it autonomously alert the fleet? Can it initiate tracking? Can it cue weapons systems? The answers depend on rules of engagement, the operational context, and the confidence level of the classification — decisions that current JADC2 authority frameworks do not address with sufficient granularity for autonomous systems.
The trust framework for autonomous platforms in JADC2 must define graduated authority levels that map to confidence thresholds, operational contexts, and communication states. In a fully connected environment with human operators in the loop, an autonomous platform might serve purely as a sensor with human decision-making for all actions. In a DDIL environment where communications are denied, the same platform may need pre-delegated authority to take specific defensive actions while maintaining constraints on offensive operations.
These authority frameworks must be technically implemented in the autonomous platforms themselves — not just documented in operational orders that assume a human will interpret them. The constraint validation and verification systems that ensure autonomous platforms operate within their authorized boundaries must be robust against both software errors and adversarial manipulation.
Building the Architecture Now
The integration of autonomous platforms into JADC2 cannot wait until the manned platform interoperability problems are solved. Autonomous systems are being fielded now, and their numbers will grow rapidly over the next decade. If they are integrated as an afterthought, the result will be a patchwork of proprietary interfaces and ad hoc solutions that undermine the interoperability JADC2 is designed to achieve.
The architectural decisions being made today in JADC2 programs will determine whether autonomous platforms are native participants in the joint command and control fabric or perpetual outsiders requiring translation layers and human intermediaries. The organizations building autonomous platforms and the organizations building JADC2 infrastructure must collaborate on standards, interfaces, and authority frameworks now — before the architecture calcifies around assumptions that exclude autonomy.
The force of the future will be a hybrid of manned and autonomous systems. The command and control architecture must be designed for that future, not retrofitted to accommodate it after the fact.
