What Is Mosaic Warfare?

Last updated: October 19, 2026

Why it matters to your mission. A rigid, linear kill chain breaks the moment one high-value platform is jammed, spoofed, or shot down, and a force built around a few exquisite systems cannot absorb that loss or recompose around it. Mosaic warfare treats the fight as many smaller, networked sensors, deciders, and effectors that a commander can tile together on the fly into a different plan for every situation. The outcome is a force that keeps functioning when pieces are lost and presents an adversary with more combinations than it can counter in the time it has to decide.

Definition

Mosaic warfare is DARPA's decision-centric concept of composing many smaller, low-cost, networked sensors, deciders, and effectors into rapidly reconfigurable force packages, or kill webs, so that commanders impose complexity on an adversary faster than it can respond. The Strategic Technology Office (STO) at the Defense Advanced Research Projects Agency coined the term, drawing on the image of a mosaic: many individual tiles that mean little alone but assemble into a larger picture, and can be reassembled into a different one.

The concept is a direct response to a specific problem. The United States long held an asymmetric edge through a small number of highly capable platforms, each engineered to do one job well. That edge erodes when adversaries field comparable systems and when the loss of one node collapses a plan built around it. Mosaic warfare inverts the bet: instead of fewer, more exquisite pieces, field more, cheaper, interchangeable ones, and win on how fast and how many ways they can be recombined.

This page explains the concept, where the term comes from, and how it relates to the data-integration and decision problems that programs like Combined Joint All-Domain Command and Control (CJADC2) are built to solve. For that connective tissue, see the pillar on CJADC2 and Open DAGIR data integration.

Key takeaways

• What it is: a way of fighting that composes many low-cost, networked platforms into adaptable kill webs rather than a few exquisite platforms in a fixed kill chain.
• Why it exists: traditional platform-centric advantage is eroding, and linear kill chains are brittle; distributing the sense, decide, and act functions makes a force resilient and harder to counter.
• The mechanism: unbundle sensing, deciding, and acting so any sensor can cue any decider and any effector, exposing many possible combinations and imposing complexity on the adversary.
• The hard part: composing and recomposing those pieces at speed depends on data that is interoperable across systems and on decision support a commander can trust and trace, not on more hardware alone.
• The payoff: a force that keeps delivering effects when individual pieces are lost, and a decision tempo an adversary cannot match.

Who Created Mosaic Warfare and When?

Mosaic warfare came out of DARPA's Strategic Technology Office, which formally outlined the vision in August 2017. STO director Tom Burns and deputy director Dan Patt are credited with the term. The founding idea, in STO's own framing, was to enable "highly complex, strategic moves by composing multiple contributing systems to enable what might be thought of as 'mosaic warfare.'"

STO's reasoning started from a strategic observation rather than a technology wish list. Advanced satellites, stealth aircraft, and precision munitions no longer guarantee an edge, because comparable high-technology components are now widely and often commercially available. At the same time, the multi-year or multi-decade development cycle for a new military system can make it obsolete before it fields, while commercial electronics refresh far faster. The response was to seek a new kind of advantage, one that comes from dynamic, coordinated, highly autonomous composable systems rather than from any single platform.

You can read DARPA's own account of the concept in DARPA Tiles Together a Vision of Mosaic Warfare, the agency's primary explainer, and in the 2017 announcement, Strategic Technology Office Outlines Vision for "Mosaic Warfare". Both are DARPA primary sources and the basis for the descriptions on this page.

What Is the Difference Between a Kill Chain and a Kill Web?

A kill chain is the sequence that turns detection into effect: find, fix, track, target, engage, assess. It is linear, and in a traditional force each link is tied to a particular platform. Break one link, and the chain stops.

A kill web unbundles those functions across many platforms so that, in DARPA's phrasing, "everything that has a sensor could be connected to everything that can make a decision, and then to anything that can take an action." Any sensor can cue any decider, which can task any available effector. That redundancy is the point: the loss of one node reroutes rather than halts, and the number of possible paths from sensing to effect grows into the thousands, which is exactly the complexity an adversary then has to plan against.

The practical takeaway is that a kill web is not just a more connected kill chain. It changes what has to be true underneath: the pieces must be composable, the data has to move between dissimilar systems, and a commander has to be able to choose a combination and understand why it was offered.

How Does Mosaic Warfare Work?

Mosaic warfare rests on three moves.

• Disaggregate the platform. Separate sensing, deciding, and acting so they live on many smaller systems instead of a few large ones. Each piece is cheaper, and the loss of any one is tolerable.
• Make the pieces composable. Build systems that can be connected and recombined without a bespoke, years-long integration effort for every pairing. DARPA has contrasted this with earlier "system of systems" approaches that were designed as a single static configuration by one integrator and proved brittle.
• Decide fast over the combinations. Expose the many possible sensor-to-decider-to-effector paths and help a commander select and adapt a force package at the speed the situation demands.

DARPA's own programs illustrate the pattern. One line of work produced a software-only, government-owned integration toolchain meant to connect heterogeneous systems across domains quickly, without replacing hardware or rewriting the systems being connected. The design choice that matters for this page is that the integration layer is non-proprietary and owned by the government, so the composition logic is not locked inside one vendor's product. That is the same ownership and interoperability principle that recurs across the Department of War's data-integration efforts.

The hardest part is not building more platforms. It is the data and decision layer that lets dissimilar systems understand each other and lets a human choose among the combinations with confidence. Hardware makes the tiles; data and reasoning let a commander assemble the picture.

How Is Mosaic Warfare Different From Decision-Centric Warfare?

The two terms are closely linked and often used together. Mosaic warfare is the DARPA concept of the composable force. Decision-centric warfare is the framing that explains what that force is for: creating and sustaining a decision-making advantage for friendly commanders while denying it to the adversary. A mosaic is the means; decision advantage is the end.

That distinction matters for how you evaluate the idea. A larger inventory of cheap, networked platforms is not, by itself, mosaic warfare. The concept only pays off if the force can decide and recompose faster than the adversary, which puts the weight on data interoperability and trustworthy decision support rather than on hardware count. For the outcome this is organized around, see decision advantage.

How Does Mosaic Warfare Relate to CJADC2?

Mosaic warfare and CJADC2 approach the same battlefield from two directions. Mosaic warfare is a warfighting concept about how forces should be composed. CJADC2 is the Department of War's program-level effort to connect sensors, data, and forces across all domains, services, and partners into one decision network. A mosaic force is unbuildable without the data backbone CJADC2 is meant to provide, and CJADC2 exists to enable exactly the fast, cross-domain composition mosaic warfare describes.

The connection is concrete. Both turn on combining data from many sources into a decision-ready picture while the government retains control of its data and systems can interoperate without being locked to one vendor. Independent oversight has documented how hard that cross-domain integration is in practice. The U.S. Government Accountability Office found that the department still needs a comprehensive framework to guide command-and-control data integration (see GAO, Defense Command and Control, GAO-25-106454, 2025). The warfighting concept is only as real as the data and decision infrastructure under it.

What Does Mosaic Warfare Require to Actually Work?

For evaluators and planners, the concept implies a short list of hard requirements. The platforms are the visible part; most of this list is data and reasoning.

1. Interoperable data across dissimilar systems. Pieces from different services, vendors, and domains have to exchange meaning, not just bytes, or they cannot be composed.
2. Government-owned integration and reasoning. The composition and decision logic should be controllable by the government, not trapped inside a single vendor's proprietary model, consistent with DARPA's own non-proprietary toolchain choice.
3. Trustworthy, traceable decision support. A commander choosing among thousands of possible combinations needs to see why an option was offered and be able to inspect it.
4. Human command preserved. The force recomposes under human direction; autonomy supports the decision rather than replacing the commander.
5. Operation in contested, disconnected conditions. Composition cannot depend on a perfect network; it has to degrade gracefully at the tactical edge.
6. Resilience through redundancy. The design assumes pieces will be lost and reroutes around them rather than failing as a whole.

How Torch.AI Approaches the Mosaic Warfare Data Problem

Torch.AI does not build weapon platforms. It builds the government-owned reasoning infrastructure that a composable force depends on: the layer that connects fragmented, multi-source data, preserves its meaning, makes relationships explicit, and routes decision-ready outputs into mission workflows. In mosaic terms, Torch.AI works on the connective tissue between the tiles, not the tiles.

That maps onto the public products. NEXUS makes data meaningful, giving dissimilar systems a shared, semantic representation so their outputs can be compared and composed rather than merely co-located. HALO makes relationships understandable through graph-based fusion, so a commander sees how sensors, tracks, and entities connect across domains. ORCUS is the data-availability layer that connects to mission data where it lives and keeps it interoperable rather than trapped in a proprietary model. The common thread is that the customer keeps control of the reasoning layer and can inspect and govern it, which is the same ownership principle the mosaic concept assumes. You can see how this is packaged as a capability on the Torch.AI software page.

This is the systems of record versus systems of reason distinction at the center of Torch.AI's approach. Mosaic warfare needs a system of reason that sits on top of existing systems of record, preserves provenance, and lets a human command the composition with confidence. For evaluators scoping that layer, request a technical walkthrough and we will run it against a representative slice of your multi-source data.

Sources

• DARPA, DARPA Tiles Together a Vision of Mosaic Warfare, darpa.mil - DARPA's primary explainer of the mosaic warfare concept, the tile metaphor, and distributed sense-decide-act kill webs.
• DARPA Strategic Technology Office, Strategic Technology Office Outlines Vision for "Mosaic Warfare", August 2017, darpa.mil - the 2017 announcement stating the composable-systems strategy and imposing-complexity rationale.
• U.S. Government Accountability Office, Defense Command and Control: Further Progress Hinges on Establishing a Comprehensive Framework, GAO-25-106454 (2025), files.gao.gov - oversight on how hard cross-domain command-and-control data integration is in practice.

Who created mosaic warfare and when?

DARPA's Strategic Technology Office outlined the vision in August 2017, with the term credited to STO director Tom Burns and deputy director Dan Patt. It was framed as composing multiple contributing systems into adaptable force packages rather than relying on a few exquisite platforms.

What is the difference between a kill chain and a kill web?

A kill chain is a linear find-to-finish sequence, usually tied to specific platforms, so breaking one link stops it. A kill web distributes sensing, deciding, and acting across many platforms so any sensor can cue any decider and effector, and the loss of a node reroutes instead of halting.

How is mosaic warfare different from decision-centric warfare?

Mosaic warfare is the composable-force concept; decision-centric warfare is the framing that explains its purpose, which is to create a decision advantage for friendly commanders while denying it to the adversary. The mosaic is the means and decision advantage is the end.

How does mosaic warfare relate to CJADC2?

Mosaic warfare is a warfighting concept about how forces are composed; CJADC2 is the department-level effort to connect sensors, data, and forces into one decision network. A mosaic force depends on the cross-domain data backbone CJADC2 is meant to provide.

What does mosaic warfare require to actually work?

Interoperable data across dissimilar systems, government-owned integration and reasoning, trustworthy and traceable decision support, preserved human command, operation in contested and disconnected conditions, and resilience through redundancy. Most of the hard requirements are about data and reasoning, not more hardware.