Also written JADC2 (Joint All-Domain Command and Control); the added C is for Combined, signaling coalition integration.

The slogan is connectivity; the substance is data. A sensor feed is worthless to a commander until it has been reconciled against everything else the force already knows, and that reconciliation is where most of the difficulty lives. CJADC2 is less a network to be built than a data-integration problem to be solved, repeatedly, under classification and at the edge.

That makes CJADC2 the mission context the rest of this hub ladders up to: you cannot integrate what you cannot first match (entity resolution), you cannot act on fragments you have not fused into one picture (multi-INT fusion), and the common picture is only decision-ready if it stays owned and traceable.

Key takeaways

• What it is: the DoD concept for integrating data across all domains and coalition partners so commanders can sense, make sense, and act faster; a way of using data and analytics, not a single system to buy.
• Why it is hard: the data is fragmented across systems that do not agree, classification constrains what can be combined, and oversight has found DoD still lacks a framework to guide and track it.
• The ownership risk: the government has flagged that relying on a single software provider for core data solutions risks vendor lock-in; the integration layer is federated, not one repository.
• What to require: government-owned control of the integration layer, classification-aware data handling, and a common picture that traces back to every source.
• The payoff: fragmented, multi-domain data becomes one briefable, defensible picture, assembled at machine speed, that a commander can act on and a coalition can share.

Why the Pentagon Needs CJADC2: The End of Swivel-Chair Analysis

The problem CJADC2 exists to solve is concrete and expensive. Today an analyst often receives inputs from one system and manually re-enters them into another, a pattern the U.S. Government Accountability Office calls "swivel-chair" analysis (GAO, Defense Command and Control, GAO-25-106454, 2025). Every manual hop costs time the mission does not have and introduces errors no one can audit. CJADC2 is the move from that model to one where the data is integrated once and reused everywhere.

The Department has made the need explicit. Its unclassified strategy frames CJADC2 as the capability to "sense, make sense, and act at all levels and phases of war, across all domains, and with partners, to deliver information advantage at the speed of relevance," organized around lines of effort that put the data enterprise first (DoD, Summary of the Joint All-Domain Command and Control (JADC2) Strategy, 2022). "Make sense" is the operative phrase: connectivity moves bits, but making sense of them is a reasoning problem over fragmented data.

The mechanism the Department has chosen for the data layer reinforces the point. The Chief Digital and Artificial Intelligence Office's Open DAGIR initiative (Open Data and Applications Government-owned Interoperable Repositories) is built to combine multi-source data while the government retains ownership and interoperability, rather than pooling everything into one proprietary platform (CDAO, Open DAGIR Fact Sheet, 2024). The architecture is deliberately federated: oversight notes that there will not be a single data repository across DoD, but a computing environment that connects existing federated data across systems.

For the mission the payoff is the same one every page in this hub returns to: fragmented, multi-domain data becomes one picture a commander can act on, assembled at machine speed, with a line back to every source so a coalition can share it and an inspector can defend it.

JADC2 vs. CJADC2: What the "Combined" Adds

Bottom line: JADC2 is the all-domain command-and-control concept; CJADC2 adds the "Combined" C to make coalition data sharing a first-class requirement rather than an afterthought. The data-integration problem is the same; CJADC2 raises the bar on releasability and partner interoperability.

Dimension	JADC2	CJADC2
Scope	Joint force across all U.S. domains	Joint force plus coalition and mission partners
What the extra "C" means	Not present	Combined: partner data sharing is a core requirement
Hardest added constraint	Cross-service data integration	Cross-service plus releasability and partner interoperability
Data-sharing challenge	Classification across services	Classification plus foreign-disclosure and releasability rules
Origin	DoD concept, strategy summarized 2022	DoD effort established 2019 (per GAO); Combined adds coalition partners

The takeaway is not that CJADC2 is a different program; it is the same all-domain concept with coalition sharing promoted to a requirement. That promotion makes classification-aware and releasability-aware data handling non-negotiable, because the picture now has to be shareable with partners who are allowed to see some of it and not the rest.

Sense, Make Sense, Act: How CJADC2 Is Supposed to Work

CJADC2 is a data flow, not a box. Following the strategy's own framing, the stages are:

• Sense. Collect observations across domains, space, air, land, sea, cyber, and the electromagnetic spectrum, from service and partner sensors that use different formats and standards.
• Integrate the data. Connect those sources through a federated data layer, normalizing enough to compare them without forcing everything into one schema or one repository.
• Make sense. Resolve records that describe the same real-world entity, fuse them into a common picture, and reason over it, so the force sees one track instead of a dozen unmatched reports.
• Decide. Present the common operational picture and decision-support to commanders, with confidence and provenance attached, so the judgment can be made and defended.
• Act and share. Communicate decisions across the joint force and to coalition partners, respecting releasability at every step.

The load-bearing stage is "make sense." Connectivity and a federated data layer get the bits into reach, but a commander needs a reconciled picture, not a bigger inbox. That is why CJADC2 depends on the same disciplines the rest of this hub covers: entity resolution decides which records are the same entity, multi-INT fusion links them into the common picture, and GraphRAG makes that picture answerable, each step preserving the line back to source.

CJADC2 vs. Related Terms

These terms travel together in command-and-control discussions and are easy to conflate. They name different layers. The table separates them.

Term	What it is	Relationship to CJADC2
Open DAGIR	A DoD initiative for government-owned, interoperable data repositories	The data-layer mechanism CJADC2 relies on; it supplies the owned, federated integration CJADC2 needs
Data fabric or data mesh	Architectural patterns for connecting distributed data without centralizing it	The technical shape of the federated layer; CJADC2's integration layer is federated, not a single store
Common operating picture (COP)	The shared display of the current situation	An output of CJADC2, only as trustworthy as the resolution and fusion beneath it
Decision advantage	Deciding and acting faster and better than the adversary	The goal CJADC2 serves; "information advantage at the speed of relevance" in the strategy's words

What Makes CJADC2 Hard

• No single repository. By design the integration layer is federated across many systems, so the hard part is reconciling data in place, not loading it into one store.
• Overly restrictive classification. Oversight has found that classification is a significant hindrance to sharing command-and-control data, and that officials were not aware of an entity working to solve it.
• Partner releasability. The "Combined" requirement means some of the picture is releasable to a partner and some is not, down to the individual record.
• Fragmentation and stovepipes. Services and entities have pursued their own data-integration efforts in isolation, which oversight warns makes the goal slower and less efficient to reach.
• Vendor lock-in. DoD has raised concern that relying on a single software provider for key data solutions could lock the Department to certain vendors, and that non-standard interfaces limit interoperability.
• The tactical edge. The picture has to hold up in disconnected, degraded, and low-bandwidth conditions, not only in a connected data center.

Why CJADC2 Data Integration Has to Be Government-Owned

The vendor-lock-in concern is not a talking point; it is an oversight finding. When the layer that integrates a force's data is a vendor's proprietary environment, the government's own data and the logic that reconciles it live somewhere it cannot fully inspect or move. For CJADC2, where the whole point is interoperability across services and partners, that is a strategic risk. The table contrasts the two acquisition models against the considerations that decide the mission.

Consideration	Typical commercial platform	Government-owned reasoning infrastructure
Control of the integration layer and logic	Held in the vendor's proprietary environment	Customer keeps control of the integration and reasoning layer
Interoperability	Often non-standard interfaces; risk of lock-in	Open, interoperable; complements existing systems
Relationship to existing systems	Often a new platform to migrate onto	Reasons over federated data in place; no rip-and-replace
Data ownership	May reside with the vendor	Government retains ownership of its data (the Open DAGIR model)
Classification and releasability	Varies	Classification- and releasability-aware by design
Where it can run	Frequently cloud-only	Enterprise to disconnected tactical edge

Government-owned does not mean the government builds everything itself or owns a vendor's underlying intellectual property. It means the customer keeps control of the mission layer, the integration and reasoning over its own data, and can inspect, govern, and evolve it rather than renting it inside a proprietary platform. Whether a specific deployment is government-owned (GOTS) or commercial (COTS) depends on the system the customer installs and purchases; for a capability meant to integrate the whole force's data, the government-owned model is the one to evaluate when ownership and interoperability are the point.

What to Require in a CJADC2 Data Capability

The comparison explains why ownership and interoperability matter; the checklist is what to require in an evaluation.

1. Government-owned and interoperable. The customer keeps control of the integration layer and data, with open interfaces, not a single-vendor lock-in.
2. Works on federated data in place. Reasons over existing systems without forcing one repository or a rip-and-replace migration.
3. Resolves and fuses, not just connects. Delivers a reconciled common picture, built on entity resolution and fusion, rather than a bigger pile of feeds.
4. Classification- and releasability-aware. Handles classification and partner-disclosure rules at the data level, during integration, not after.
5. Provenance-preserving. Every element of the common picture traces back to its source and can be inspected and defended.
6. Runs where the mission runs. Enterprise, on-premise, classified, and disconnected or degraded edge.
7. Human judgment preserved. Commanders and analysts see confidence and can interrogate the picture, not just receive it.

Evaluating a capability? The seven requirements above are the backbone of a CJADC2 data-integration evaluation you can score vendors against. Bring them to a scoping call and we will walk each one against your environment: request a technical walkthrough.

How Torch.AI Supports CJADC2

Torch.AI builds reasoning infrastructure the customer can own and govern, offered as a government-owned (GOTS) deployment when a mission requires it, aligned with the Open DAGIR model of keeping data owned and interoperable. The reasoning layer connects to mission data where it lives across services and domains. ORCUS ingests and normalizes the fragmented, multi-source feeds, including unstructured text, without forcing them into one repository. NEXUS reads the unstructured sources for the entities and relationships buried in reporting. HALO resolves records that describe the same entity and fuses them into a common picture whose every element traces back to source, respecting classification and releasability throughout. You can see how this is packaged as a capability on the Torch.AI software page.

Because it reasons over federated data in place rather than replacing the systems that hold it, the authoritative sources stay intact and interoperable, not locked inside a proprietary model. This is the systems of record versus systems of reason distinction at the center of Torch.AI's approach: the reasoning layer acts as a system of reason on top of the force's existing systems of record, delivering the reconciled, shareable picture CJADC2 calls for without the vendor lock-in oversight has warned against.

Torch.AI's approach is built for the conditions this page describes: all-domain, multi-source data; classification- and releasability-aware integration; a common picture traceable to its sources; and operation from the enterprise to the disconnected tactical edge.

For evaluators scoping a capability, see how Torch.AI delivers resolution, fusion, and government-owned data integration on multi-domain data, deployable government-owned, on the software page, or request a technical walkthrough and we will run it against a sample of your own multi-domain data, with provenance traced end to end.

Sources

• U.S. Department of Defense, Summary of the Joint All-Domain Command and Control (JADC2) Strategy (2022), media.defense.gov - the unclassified strategy: sense, make sense, act at the speed of relevance, with the data enterprise as a line of effort.
• Chief Digital and Artificial Intelligence Office, Open DAGIR Fact Sheet (2024), media.defense.gov - government-owned, interoperable repositories for combining multi-source data while the government retains ownership.
• U.S. Government Accountability Office, Defense Command and Control: Further Progress Hinges on Establishing a Comprehensive Framework, GAO-25-106454 (2025), files.gao.gov - the swivel-chair problem, the federated-not-single-repository approach, overly restrictive classification, and the vendor lock-in concern.

Frequently Asked Questions

What is the difference between JADC2 and CJADC2? JADC2 is the all-domain command-and-control concept; CJADC2 adds the "Combined" C to make coalition and mission-partner data sharing a first-class requirement, which raises the bar on releasability and partner interoperability. The underlying data-integration problem is the same. See the JADC2 vs. CJADC2 table.

Is CJADC2 a system I can buy? No. Oversight is explicit that CJADC2 is not a single system but a way of using data and analytics to make and communicate decisions. What a program actually acquires is the data-integration and reasoning capability underneath it, which is why ownership, interoperability, and classification handling are the real evaluation criteria.

How does Open DAGIR relate to CJADC2? Open DAGIR is the data-layer mechanism: government-owned, interoperable repositories that let the force combine multi-source data while the government retains ownership. CJADC2 needs exactly that owned, federated integration to work, which is why the two are usually discussed together.

Why is data integration the hard part of CJADC2? Because the same entity arrives from many systems that were never built to agree, under classification rules that limit what can be combined. Connecting the systems is necessary but not sufficient; the force needs the data reconciled into one picture, which depends on entity resolution and fusion, not just a network.

Does CJADC2 require a single central database? No. DoD has stated there will not be a single data repository across the Department; the integration layer is federated, connecting existing data across systems. That is why a capability has to reason over data in place rather than demand a migration into one store.

Can CJADC2 data integration run on classified and disconnected networks? It has to. A mission-grade capability handles classification and releasability during integration and can operate government-owned in classified and disconnected or degraded environments, not only as a cloud service.

What does government-owned CJADC2 integration mean? It is a deployment and ownership model (GOTS) in which the customer keeps control of the integration layer, the reasoning logic, and the data, with open interfaces that avoid vendor lock-in, and can run them in classified or disconnected environments. The same capability can also be delivered commercially (COTS); which applies depends on the system the customer installs and purchases.