.svg){kind=icon}
Learn
JADC2 (Joint All-Domain Command and Control) is the Department of Defense effort to connect sensors, data, and forces across all services and domains into a single decision network, and CJADC2 is the same effort with a leading 'Combined,' extending it to allies and mission partners.
Last updated: October 18, 2026
Why it matters to your mission. A commander who cannot see what an ally sees, in time to act, is fighting a coalition war on single-service data. JADC2 and CJADC2 name the Department of War's effort to connect sensors, data, and forces into one decision network, and the "Combined" is the part that lets partner forces into that picture. The outcome is a shared, trusted understanding of the fight that crosses service and national boundaries fast enough to decide first.
JADC2 (Joint All-Domain Command and Control) is the Department of Defense effort to connect sensors, data, and forces across all services and domains into a single decision network, and CJADC2 is the same effort with a leading "Combined," extending it to allies and mission partners. They are not two competing programs. CJADC2 is the version of JADC2 that assumes the United States rarely fights alone, so the data has to reach coalition forces, not only joint U.S. ones.
The distinction is small in wording and large in engineering. Adding "Combined" means the same track, the same contact, the same intelligence has to cross a classification and releasability boundary that was built, on purpose, to keep foreign nationals out. That is where the hard problem lives, and it is why the "C" is worth a page of its own.
Key takeaways
The difference is one word, and it reorders the whole problem. JADC2 is about making the U.S. joint force fight as one connected system instead of as separate service networks. CJADC2 keeps that goal and adds the harder constraint: the connected system has to include allies and mission partners, which means data has to move across national boundaries under the rules that govern foreign disclosure.
Put plainly, JADC2 is the "fight joint" ambition and CJADC2 is the "fight joint and combined" ambition. The sensors-to-decisions plumbing is shared. What the "Combined" adds is a releasability problem on top of an integration problem: every shared record now has to carry who may see it, enforced as the data moves, not decided after a leak.
The table below separates the two at the level that matters to an architect.
| Dimension | JADC2 | CJADC2 |
|---|---|---|
| What the acronym means | Joint All-Domain Command and Control | Combined Joint All-Domain Command and Control |
| Primary scope | U.S. joint force across all services and domains | U.S. joint force plus allies and mission partners |
| The hardest constraint | Interoperability across service networks and legacy systems | That, plus foreign-disclosure and releasability across national boundaries |
| Classification pressure | Cross-domain between U.S. levels | Cross-domain plus the "Not Releasable to Foreign Nationals" barrier to partner sharing |
| Core engineering challenge | Combine many sources into one decision-ready picture | The same, with releasability enforced per record for coalition sharing |
| Governing framing | All-domain command and control | The same vision, rescoped as combined |
CJADC2 does not replace JADC2. The "Combined" turns a data-integration program into a data-integration-and-disclosure program, and the second is strictly harder.
Because the United States fights with allies, and the original name did not say so. The joint vision connected the services to each other, but modern operations are combined by default, and partner forces could not fully enter a picture scoped only as "joint." Adding "Combined" made the coalition an explicit requirement of the architecture rather than an afterthought bolted on later.
Independent oversight makes clear why this is not a cosmetic rename. The U.S. Government Accountability Office, in Defense Command and Control: Further Progress Hinges on Establishing a Comprehensive Framework (GAO-25-106454, 2025), found that overly restrictive classification policies, in particular the "Not Releasable to Foreign Nationals" designator, significantly impede the information sharing that a combined force depends on. The same report found that military services pursue their command-and-control efforts largely in isolation and without clear common goals, and that proprietary interfaces and vendor lock-in restrict the data exchange the effort requires. The "C" names the ambition; GAO names the gap between the ambition and today.
CJADC2 is better understood as a connecting framework than as a single program of record you can buy. It is a goal state, a way of combining many existing and future systems so they behave as one decision network, rather than one product that delivers that outcome on its own. GAO's central finding reinforces this: without a comprehensive framework to guide investments and measure progress, the services tend to build command-and-control capabilities in isolation.
For an architect, the consequence is simple. There is no single CJADC2 box to install. There is a set of data, interoperability, and releasability requirements that many systems have to meet in common, which is exactly why the integration and governance layer, not any one sensor or application, is where the effort succeeds or stalls.
AI fits where the volume of data outruns human attention: correlating sensor reporting, resolving which records describe the same real-world object, and surfacing the few things a commander needs to see across a coalition picture. The constraint is that a combined force cannot act on an answer it cannot trace or govern. A shared track that no one can explain, or that silently crossed a releasability line it should not have, is a liability, not an advantage.
So AI in CJADC2 has to be decision support that stays auditable and keeps releasability enforced at the data layer. The model helps make sense of the picture faster; the governance decides what a partner may see and leaves a trail back to the source. Speed without that governance is how a combined network leaks or decides on fiction.
Torch.AI builds government-owned reasoning infrastructure that connects to data where it already lives, which is the layer CJADC2 lives or dies on. Rather than replacing systems of record, the reasoning layer complements them: it connects fragmented, multi-source data, preserves meaning across systems, makes relationships explicit, and routes outputs into mission workflows, so a joint or combined force can reason over one coherent picture at machine speed.
Where the public products fit: NEXUS makes multi-source data meaningful, turning fragmented records into a semantic representation the mission can reason over. HALO makes the relationships understandable, fusing resolved entities into a graph an analyst can trust and trace. For maritime and Navy or joint deployments, that capability is delivered as ORCUS. Because the infrastructure can be deployed government-owned, the customer keeps control of the integration and the releasability logic rather than renting them inside a vendor's proprietary environment, which is directly responsive to the vendor lock-in GAO flagged. Ownership varies by deployment and purchase (government-owned or commercial); the point is that the government-owned model is available when the mission needs it. You can see how this is packaged as a capability on the Torch.AI software page.
This is the systems of record versus system of reason distinction at the center of Torch.AI's approach: existing systems keep recording the authoritative data, and the reasoning layer on top turns it into a shared, governable, releasable picture a coalition can act on.
Scoping a CJADC2 or coalition data layer? Bring these seven requirements to a technical walkthrough and we will run them against your environment and a sample of your multi-source data: request a technical walkthrough.
CJADC2 is JADC2 with a leading 'Combined.' JADC2 connects the U.S. joint force across all services and domains into one decision network; CJADC2 keeps that goal and extends it to allies and mission partners, which adds a foreign-disclosure and releasability problem on top of the integration problem.
To make coalition operations an explicit part of the architecture. The United States fights with partners, so the connected network has to reach partner forces. GAO-25-106454 (2025) found that restrictive classification policies, especially the 'Not Releasable to Foreign Nationals' marking, significantly impede the information sharing a combined force needs.
It is closer to a connecting framework than a single program of record. It is a goal state for combining many existing and future systems into one decision network, which is why GAO found the services building command-and-control capabilities in isolation without a comprehensive framework to align them.
AI correlates sensor data, resolves records that describe the same object, and surfaces what a commander needs from a coalition picture faster than people can by hand. It has to stay auditable and keep releasability enforced, because a combined force cannot act on an answer it cannot trace or govern.
Interoperability without vendor lock-in, releasability enforced at the data layer, multi-source and all-domain coverage, a government-owned option, provenance and auditability, operation in disconnected and classified environments, and preserved human judgment.
Describe the problem.
Define the constraints. We will structure the session.
No demo.
No slide deck.
Real work.
Describe the problem.
Define the constraints. We will structure the session.
No demo.
No slide deck.
Real work.
