JADC2 FAQ

JADC2 - Joint All-Domain Command and Control - is the DoD's strategic concept for linking sensors, decision-makers, and effectors across all warfighting domains (land, sea, air, space, cyber, EMS) into a unified, machine-speed kill chain. It replaces the legacy model where each service fights its own war with incompatible data links and proprietary systems.

The concept is sound. The execution has been uneven. Top-down JADC2 programs attempt to build a single pan-DoD enterprise architecture. Sensor-up JADC2 - the only model that has actually demonstrated combat relevance - builds edge-deployable fusion and decision capability at the tactical unit and connects it upward as bandwidth and authority permit.

Full technical reference: What is JADC2?.

The Air Force's contribution to JADC2 is the Advanced Battle Management System (ABMS), intended to link airborne sensors, space assets, ground command nodes, and strike platforms through a common data fabric. ABMS has struggled to demonstrate operational outcomes at the pace Congress has expected, and funding has been repeatedly restructured.

The Air Force's pragmatic JADC2 contribution has increasingly shifted toward specific enabling capabilities - edge compute at the cockpit, tactical AI for target recognition, open mission systems (OMS) standards for payload interoperability - rather than a single monolithic ABMS program. That shift aligns with the sensor-up model that survives contact with contested environments.

The JADC2 strategy is the DoD's plan to connect any sensor to any shooter, any time, anywhere - constrained only by policy and physics rather than by incompatible data links and proprietary service systems. The unclassified strategy document frames four lines of effort: data, human integration, technology, and nuclear C2/C3 integration.

The strategy is correct in its ambition. The operational gap is between the strategy document and the systems actually deployed to tactical units. Closing that gap requires fusion and decision capability that runs at the edge, survives degraded connectivity, and works with sensors already in the field rather than demanding purpose-built architectures from scratch. See Why JADC2 Needs Sensor Fusion at the Edge.

JADC2 architecture refers to the technical and organizational structure connecting sensors, command nodes, and effectors across domains. The reference architecture includes standardized data schemas, open APIs, zero-trust security, edge-to-cloud compute distribution, and common time/position services.

The architectural debate that actually matters is between cloud-centric JADC2 (fusion and policy run in a central data center, units consume the result) and edge-centric JADC2 (every unit runs the full stack locally, connectivity enriches but does not enable). Cloud-centric architectures look great in peacetime exercises and fail immediately in contested environments where SATCOM, GPS, and tactical data links are under attack. Edge-centric is the only model that survives Russian-grade EW or Chinese A2/AD posture. Empyrean is designed edge-first by default - see our capabilities.

JADC2 is a Department of Defense concept, not a single program of record. Implementation is distributed across the services (Army Project Convergence, Navy Project Overmatch, Air Force ABMS), the Joint Staff (J-6 coordination), OSD (CDAO for data and AI), the Combatant Commands (especially USINDOPACOM and USSPACECOM), and the DoD CIO.

This distribution is both a feature and a bug. Feature: each service builds to its own operational problem. Bug: integration across services is nobody's full-time job, and interoperability gaps emerge that nobody owns. The recent shift toward CJADC2 (Combined JADC2) expands the scope further to include allied integration, which is where most near-peer fights will actually require the capability.

Palantir Foundry and Gotham are used across multiple JADC2-adjacent programs for data integration, intelligence fusion, and operational planning. Palantir's strength is large-scale data integration, analytics, and user-facing workflow - well-suited to intelligence and mission planning at theater and strategic echelons.

Palantir was not architected as an edge-deployable tactical fusion platform, and its footprint in the kill-chain-critical tactical fusion role is limited. That is a natural division of labor: strategic-echelon data integration and tactical-edge sensor fusion are genuinely different engineering problems. Empyrean operates in the tactical-edge fusion layer - below the Foundry/Gotham altitude - with a sensor-up architecture, policy enforcement, and a common operational picture that survives DDIL conditions.

The Army's JADC2 contribution is Project Convergence - the annual campaign of learning that tests sensor-to-shooter kill chains across services and increasingly with allies. Project Convergence has produced real operational learning, particularly around autonomous sensor cueing, AI-assisted targeting, and cross-service data exchange.

Project Convergence '24 and its successors have continued to expose the same friction points: data normalization across vendors, identity provenance across sensor classes, ROE and engagement policy enforcement at machine speed, and degraded-connectivity operation. These are exactly the problems edge-deployed fusion platforms are built to solve. The Army's C5ISR Center and PEO IEW&S continue to drive requirements that lean sensor-up.

The Navy's JADC2 contribution is Project Overmatch, focused on the maritime kill chain and the distributed naval force. Project Overmatch is largely classified, which is deliberate - the Navy has taken the position that publicizing the specifics undermines the capability.

The unclassified parts center on resilient naval networking (Mesh, BACN-class relays, LEO constellation integration), data-link modernization beyond Link 16, and distributed lethality enabled by organic sensor-to-shooter chains across a dispersed fleet. The Navy's JADC2 problem is uniquely shaped by maritime geometry - long sensor baselines, denied GPS, contested SATCOM, and a strong bias toward autonomous operation by individual platforms when the network degrades.

Joint All-Domain Operations (JADO) is the doctrine of executing military operations that integrate capabilities across all warfighting domains - land, sea, air, space, cyber, and the electromagnetic spectrum - against adversaries whose operational reach crosses the same domains. JADO is the operational doctrine that JADC2 (the C2 concept) is meant to enable.

The doctrinal shift from single-domain dominance to all-domain integration is a response to near-peer adversaries who have explicitly built forces to contest the US across every domain simultaneously. JADO assumes that no domain will be uncontested and that friendly forces must be able to rapidly shift effects and assets across domains as contests emerge. The C2 systems underneath JADO have to keep up - which is where JADC2 lives.

Joint All-Domain Command and Control (JADC2) is the command and control concept that makes Joint All-Domain Operations possible. It is the data, decision, and execution layer connecting sensors to shooters across all warfighting domains.

See What is JADC2? for the full technical reference.

The principles of Joint All-Domain Operations center on rapid cross-domain effect generation, cognitive and decision advantage, resilient C2, and assumed contest in every domain. Doctrine publications frame variations of these, but the load-bearing ones are: see first, understand first, decide first, act first - across domains, against adversaries doing the same.

Getting those principles operationalized requires sensor coverage that is fused rather than compartmentalized, decision processes that are automated where they can be and policy-enforced where they must be, and C2 architectures that survive degraded connectivity. The principles themselves are straightforward. The engineering to execute them consistently against a contesting adversary is the hard part.

Joint All-Domain Operations doctrine is codified across service and joint publications including JP 3-0 (Joint Operations), updated service doctrine (FM 3-0 for the Army, AFDP 3-99 for the Air Force), and emerging joint publications on JADC2 and multi-domain effects integration. The doctrine continues to evolve as the services learn from Project Convergence, Project Overmatch, ABMS demonstrations, and ongoing operations.

Doctrine lags capability in some areas (autonomous effects, AI-assisted decision-making, cyber-physical convergence) and leads in others (cross-domain fires coordination, multi-domain targeting). The useful question for an operator is not "what does doctrine say" but "what can my C2 stack actually execute across domains when the bandwidth drops and the timing matters."

JADO is the acronym for Joint All-Domain Operations - the doctrinal framework for conducting integrated operations across land, sea, air, space, cyber, and the electromagnetic spectrum. It is the operational-level doctrine that JADC2 is designed to support.

The eight principles of Joint All-Domain Operations as articulated in USAF doctrine are: Mission Command, Global Integration, Sensor-Shooter Integration, Information Advantage, Decision Advantage, Operational Agility, Joint and Combined Arms Integration, and Domain Flexibility. Variations exist across service doctrine publications; the underlying ideas are consistent.

All eight presuppose a C2 architecture that can move data, decisions, and effects across domains at speed - which is why JADC2 is the required enabling layer.

Joint All-Domain Operations wargames are exercises that rehearse cross-domain kill chains, decision cycles, and coordination problems before they have to be executed live. The flagship venues are Project Convergence (Army-led, joint and combined participation), the Navy's Fleet Problem series, the Air Force's Red Flag and Emerald Warrior, and the Joint Staff's Global Integration exercises.

Wargames are most useful when the tools used in the game are the same tools used in operations - same fusion engine, same COP, same policy enforcement. Running a wargame on a bespoke simulation stack and then operating with a completely different C2 system produces confident, trained operators who are unfamiliar with the actual tools they'll use under fire. Empyrean's Simulation & Wargaming engine runs the same fusion and policy pipeline as the operational platform, so training transfers directly.

• What is JADC2? - full technical reference on the sensor-up case against top-down JADC2
• Why JADC2 Needs Sensor Fusion at the Edge - the architectural argument
• Simulation & Wargaming - wargame with the same tools you operate with
• Sensor Fusion - the edge-deployable fusion layer underneath JADC2