.svg){kind=icon}
Learn
Multi-domain operations (MDO) is the U.S. Army and joint operational concept of employing combined-arms capabilities across land, air, maritime, space, and cyberspace simultaneously to create and exploit relative advantages that defeat an enemy force.
Last updated: October 23, 2026
Why it matters to your mission. An adversary that can contest you in every domain at once cannot be beaten one domain at a time. Multi-domain operations are the answer: a way of fighting that converges land, air, maritime, space, and cyberspace effects fast enough to present the enemy with more dilemmas than they can solve. The hard part is not the firepower. It is the shared understanding. Converging effects across domains and services requires that distributed forces reason over the same data at machine speed, which is why MDO is as much a data problem as a doctrine problem. The outcome of MDO done well is decision advantage: friendly forces act coherently across domains faster than the adversary can react.
Multi-domain operations (MDO) is the U.S. Army and joint operational concept of employing combined-arms capabilities across land, air, maritime, space, and cyberspace simultaneously to create and exploit relative advantages that defeat an enemy force. The central idea is that a peer adversary who can contest every domain is best defeated not sequentially but through the convergence of effects from many domains at once, imposing dilemmas faster than the adversary can respond.
The U.S. Army codified MDO as its capstone operational concept in Field Manual 3-0, Operations (2022), which defines multidomain operations as "the combined arms employment of joint and Army capabilities to create and exploit relative advantages that achieve objectives, defeat enemy forces, and consolidate gains on behalf of joint force commanders." The operative words are combined arms and joint. MDO is not a new weapon. It is a way of orchestrating capabilities that already exist, across domains and services, into a single coherent effort.
Key takeaways
Multi-domain operations are conducted across five warfighting domains: land, air, maritime, space, and cyberspace. The premise of MDO is that these domains are no longer separable in practice. A modern peer adversary contests all of them at once, so a force that can only fight well in one or two is already at a disadvantage. FM 3-0 (2022) frames the operational environment through five physical domains and three dimensions, the physical, information, and human, that cut across all of them.
| Domain | What it covers | Why it matters to MDO |
|---|---|---|
| Land | Ground forces, maneuver, fires, and logistics | The domain where territory is held and gains are consolidated |
| Air | Rotary and fixed-wing aircraft, air defense, airspace control | Delivers rapid effects and protects the force from air and missile threats |
| Maritime | Surface, subsurface, and littoral operations | Projects power and sustains distributed forces across sea lines |
| Space | Position, navigation, timing, satellite communications, and ISR | Enables nearly every other domain; losing it degrades the whole force |
| Cyberspace | Networks, data, and the electromagnetic spectrum (EMS) | Where command, control, and the shared data picture live or fail |
The information and human dimensions run through all five. An effect in cyberspace can shape perception in the human dimension; a space outage degrades the information that every physical domain depends on. MDO treats these as one interconnected problem rather than five separate fights, which is precisely why it demands a common data and reasoning layer underneath the force.
MDO is the operational concept, the way forces fight across all domains, while Joint All-Domain Command and Control (JADC2, now often CJADC2) is the command-and-control and data effort that makes fighting that way possible. They are frequently conflated, but keeping them distinct matters: MDO describes the desired outcome, and JADC2/CJADC2 is a principal enabler of it, not a synonym for it.
The DoD Summary of the JADC2 Strategy (2022) defines the effort as intended "to produce the warfighting 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." The same document is explicit that "as an approach, JADC2 transcends any single capability, platform, or system." The "combined" in CJADC2 reflects an added emphasis on allies and partners. In short, MDO says fight across all domains at once; JADC2/CJADC2 is the C2 and data architecture that lets a commander actually do it.
| Aspect | Multi-domain operations (MDO) | JADC2 / CJADC2 |
|---|---|---|
| What it is | An operational concept for how forces fight | A command-and-control and data architecture that enables it |
| Primary authority | Army FM 3-0 (2022); TRADOC Pam 525-3-1 (2018) | DoD JADC2 Strategy (2022); DoD Chief Digital and AI Office |
| Core idea | Converge effects across all domains to impose dilemmas | Sense, make sense, and act across all domains at the speed of relevance |
| The failure it addresses | Fighting domain-by-domain against a peer who contests all | Not connecting the sensors, data, and decision-makers that MDO requires |
This distinction is where the data problem becomes unavoidable. You can hold the MDO concept perfectly and still fail if the data that connects sensors to decision-makers is fragmented, late, or untrustworthy. The relationship between the two is covered in more depth in JADC2 vs CJADC2 and the CJADC2 architecture.
MDO is the way of fighting; JADC2 connects it
MDO says fight across all domains at once. JADC2/CJADC2 is the command-and-control and data architecture that lets a commander actually do it, which is why the two are often conflated.
You can hold the MDO concept perfectly and still fail if the data that connects sensors to decision-makers is fragmented, late, or untrustworthy.
The foundational articulation of MDO, TRADOC Pamphlet 525-3-1, The U.S. Army in Multi-Domain Operations 2028 (2018), solves the problem posed by peer adversaries through three interrelated tenets: calibrated force posture, multi-domain formations, and convergence. These tenets remain the clearest statement of what MDO requires of a force, even as the concept matured into FM 3-0.
| Tenet | What it means |
|---|---|
| Calibrated force posture | The combination of position and the ability to maneuver across strategic distances, so forces are where they need to be and can move when required |
| Multi-domain formations | Formations with the capacity, capability, and endurance to operate across multiple domains in contested spaces against a near-peer adversary |
| Convergence | The rapid and continuous integration of capabilities across all domains, the electromagnetic spectrum, and the information environment to overmatch the enemy across domains at once |
TP 525-3-1 is explicit that these tenets are "all enabled by mission command and disciplined initiative." That phrase is doing real work. Convergence at machine speed is impossible if subordinate commanders cannot act on a shared, trusted understanding without waiting for permission. The tenets describe a force that is postured, organized, and informed well enough to converge effects faster than the enemy can counter them, which again points back to the quality and trustworthiness of the underlying data.
Convergence is the rapid and continuous integration of capabilities from multiple domains, the electromagnetic spectrum, and the information environment to create effects an adversary cannot counter using single-domain means. It is the mechanism at the heart of multi-domain operations: the point where the concept becomes an actual advantage on the battlefield.
TRADOC Pamphlet 525-3-1 describes convergence as achieving "overmatch" through "cross-domain synergy and multiple forms of attack," imposing complexity on the enemy "in ways not achievable through single domain alternatives." FM 3-0 (2022) carries the idea forward, framing convergence as the concerted employment of capabilities from multiple domains against combinations of objectives to create effects against a system, formation, capability, or decision-maker.
The reason convergence is hard is that it is a data and timing problem before it is a fires problem. To converge a space-based sensor, a cyber effect, and a ground or air strike against the same target window, every contributing element has to be working from the same picture of where the target is, what is friendly, and what the commander intends, at the same moment. If those elements are reasoning over fragmented, conflicting, or stale data, convergence degrades into a sequence of separate actions, which is exactly the single-domain fight MDO is designed to avoid. Convergence is why MDO cannot be separated from the problem of a common, trustworthy data layer.
Multi-domain operations depend on data and AI because convergence across domains is, fundamentally, a problem of connecting fragmented information fast enough to act. The capabilities already exist in each domain. What does not come for free is the shared, trusted understanding that lets distributed forces across land, air, maritime, space, and cyberspace reason over the same picture at the same time.
Two things make this a data and AI problem rather than a doctrine problem alone.
First, the data is fragmented across domains, services, and systems. A single targeting decision can draw on a space-based sensor, a maritime track, a cyber indication, and a ground report, each sitting in a different system with a different format and owner. No individual source resolves the picture. The picture only exists in the correlation across them, and correlating fragmented multi-source data at machine speed is a data infrastructure problem. The DoD JADC2 Strategy names the goal plainly: to "sense, make sense and act." The "make sense" step is where most of the difficulty lives, and it is a reasoning problem over data.
Second, the decisions have to be trustworthy and traceable. The U.S. Government Accountability Office has repeatedly flagged that progress on connecting the force hinges on data and governance rather than new sensors. Its report on defense command and control (GAO-25-106454) underscores that integrating data across the services and establishing the underlying management approach, not acquiring more platforms, is the harder and more decisive task. A commander converging effects across domains cannot act on a picture they cannot trust or trace back to its source. This is where MDO connects to data provenance for AI and to the broader pursuit of decision advantage: the advantage is only real if the understanding underneath it is defensible.
The through-line is that MDO in practice depends on being able to connect, correlate, and trust fragmented data across every domain at machine speed. That is a reasoning infrastructure problem before it is a doctrine problem.
Torch.AI does not conduct multi-domain operations or sell a C2 system, and this page is not a claim to either. What Torch.AI builds is the government-owned reasoning infrastructure that the data-dependent side of MDO relies on: the ability to connect fragmented, multi-source data across domains into a coherent picture at machine speed while keeping every element traceable to its source.
The relevant capability is the "make sense" layer between sensing and acting. Converging effects means pulling data out of many systems across domains, resolving when separate records describe the same entity or event, and surfacing the relationships a commander needs, without trapping that data in a proprietary model. ORCUS provides the data-availability layer that connects to existing sources and preserves provenance. NEXUS applies semantic representation so unstructured records across domains become something a system can correlate. HALO fuses resolved entities and relationships into a graph a commander or analyst can inspect and trace. Because this runs as a system of reason on top of existing systems of record, the authoritative sources stay intact, and in a government-owned deployment the force keeps control of the layer where fragmented, cross-domain data becomes shared understanding. See how this is packaged on the Torch.AI software page.
For evaluators, the fit is specific: if your MDO challenge is that the data needed to converge effects is scattered across domains and systems faster than anyone can correlate it, that is a data and reasoning problem, and it is the one this infrastructure is built for. Request a technical walkthrough and we will run it against a representative slice of your own multi-source data, with provenance traced end to end.
Multi-domain operations evolved from AirLand Battle, the 1980s doctrine that integrated air and ground action against Soviet forces. As adversaries built capabilities to contest the United States in space, cyberspace, and the electromagnetic spectrum, air and land integration alone was no longer sufficient. The Army introduced "Multi-Domain Battle" in 2016, formalized the broader concept in TRADOC Pamphlet 525-3-1, The U.S. Army in Multi-Domain Operations 2028 (2018), and then made it approved capstone doctrine with FM 3-0, Operations, on October 11, 2022. In parallel, the joint force pursued JADC2 and then CJADC2 as the command-and-control approach to connect the domains, with the DoD Chief Digital and Artificial Intelligence Office delivering an initial CJADC2 capability in 2024. The arc runs from integrating two domains to orchestrating five, and at each step the binding constraint shifted further toward data and command and control.
MDO doctrine is settled. The modern gap is the data capability underneath it. If you are evaluating infrastructure to support convergence and a common operating picture across domains, require:
Evaluating a capability? Bring these six requirements to a scoping call and we will walk each one against your environment: request a technical walkthrough.
Multi-domain operations are conducted across five warfighting domains: land, air, maritime, space, and cyberspace. FM 3-0 (2022) also frames the operational environment through three dimensions, the physical, information, and human, that cut across all five domains. The premise of MDO is that a peer adversary contests all domains at once, so they must be treated as one interconnected problem.
MDO is the operational concept for how forces fight across all domains, while JADC2 (now often CJADC2) is the command-and-control and data architecture that makes fighting that way possible. MDO is the desired outcome; JADC2/CJADC2 is a principal enabler of it. The DoD JADC2 Strategy describes the goal as the capability to sense, make sense and act across all domains, and states that JADC2 transcends any single capability, platform, or system.
TRADOC Pamphlet 525-3-1 (2018) defines three interrelated tenets of MDO: calibrated force posture, multi-domain formations, and convergence, all enabled by mission command and disciplined initiative. Calibrated force posture is about position and the ability to maneuver; multi-domain formations have the capacity to operate across domains; and convergence is the integration of capabilities across domains to overmatch the enemy.
Convergence is the rapid and continuous integration of capabilities from multiple domains, the electromagnetic spectrum, and the information environment to create effects an adversary cannot counter with single-domain means. TRADOC Pamphlet 525-3-1 describes it as achieving overmatch through cross-domain synergy and multiple forms of attack. Convergence is fundamentally a data and timing problem: every contributing element must work from the same trusted picture at the same moment.
Because converging effects across domains requires connecting fragmented information fast enough to act, and that data sits in different systems, formats, and owners across each domain and service. The picture only exists in the correlation across those sources, and correlating multi-source data at machine speed while keeping it trustworthy and traceable is a reasoning infrastructure problem. The JADC2 Strategy make sense step and GAO findings on data integration both point to data, not more sensors, as the decisive challenge.
MDO is the U.S. Army's capstone operational concept, codified in FM 3-0 (2022), but it is inherently joint. FM 3-0 defines it as the combined arms employment of joint and Army capabilities on behalf of joint force commanders, and the joint force pursues the enabling command and control through JADC2/CJADC2. The term all-domain operations is often used for the broader joint framing of the same idea.
Describe the problem.
Define the constraints. We will structure the session.
No demo.
No slide deck.
Real work.
Describe the decision you need to converge. We will scope a working session around your multi-domain data. No concept briefing. Your mission data. Real work.
