What JADC2 stands for
The acronym expands to Joint All-Domain Command and Control. Each word identifies a different design obligation. “Joint” means the armed services must work through shared mission threads rather than isolated service systems. “All-Domain” means command and control must account for air, land, maritime, space, cyberspace, the electromagnetic spectrum, and the information environment. “Command” concerns lawful direction, priorities, delegated authority, and accountability. “Control” concerns the processes and technical means used to monitor, coordinate, communicate, and adjust execution.
The words should not be compressed into a generic label for networking. JADC2 is about producing better command and control across organizational and technical boundaries, not merely moving more data faster.
Joint
The services, combatant commands, defense agencies, intelligence organizations, and mission partners must contribute to and consume shared mission outcomes.
All-Domain
Relevant sensing, transport, decision, support, and effect capabilities may originate in different physical and digital domains.
Command
People and institutions establish intent, priorities, authorities, prohibitions, risk acceptance, and responsibility.
Control
Processes and systems maintain state, distribute decisions, coordinate action, measure results, and adapt when conditions change.
Research basis: KW-RPT-007, KW-RPT-013, and KW-RPT-044.
JADC2 is an enterprise approach—not one product
JADC2 is broader than a network, cloud, data fabric, command application, artificial-intelligence model, or service modernization program. It is the enterprise combination of people, organizations, doctrine, authorities, data, transport, compute, applications, security, training, acquisition, testing, and partner arrangements needed to improve joint command and control.
That scope matters because no single technical layer can deliver the outcome by itself. A high-bandwidth link does not make data understandable. A common data model does not establish trust. A trusted identity does not establish releasability. A recommendation engine does not create command authority. A connected weapon does not have permission to act merely because a route exists.
- Not one universal network that replaces every existing transport.
- Not one program of record with a single owner, cost baseline, and delivery date.
- Not a requirement to connect every sensor directly to every effector.
- Not an automatic sensor-to-shooter loop.
- Not a transfer of legal, command, or force authority to software.
- Not proof that every service system or coalition partner already interoperates.
Public oversight and the KillWebs corpus treat JADC2/CJADC2 as a warfighting function and enterprise approach rather than a single bounded product. Research basis: KW-RPT-007, KW-RPT-013, and KW-RPT-038.
The operating idea: sense, make sense, and act
Public JADC2 strategy describes a recurring command-and-control cycle: sense the environment, make sense of the available information, and act through an authorized organization. The three verbs are simple; the engineering and governance beneath them are not.
-
01
Sense
Collect observations, status, warnings, intelligence, logistics, cyber, space, environmental, and partner information. Preserve source identity, time, uncertainty, sensitivity, and provenance instead of passing a bare coordinate or label.
-
02
Make sense
Fuse and compare evidence, maintain state, expose contradictions, estimate uncertainty, identify feasible options, and show what is missing. Machine assistance can accelerate this work, but it must not launder uncertainty into false certainty.
-
03
Act
Issue an authorized decision, task an appropriate organization, coordinate execution, assess the outcome, and feed the result back into the shared picture. “Act” includes command, maneuver, protection, sustainment, cyber, electromagnetic, information, and other effects; it does not inherently mean automatic force application.
Kill chain, kill web, JADC2, and CJADC2 are different levels
A useful shorthand is: the chain is the selected route, the web is the option space, JADC2 is the enterprise that makes joint routes possible, and CJADC2 makes the partner dimension explicit.
| Concept | Primary question | Unit of analysis | What it does not establish |
|---|---|---|---|
| Kill chain | How does one selected process move from sensing through decision, action, and assessment? | One ordered mission thread | Alternative paths, enterprise interoperability, or partner integration |
| Kill web | Which technically feasible, trusted, policy-compliant, and authorized pathways can satisfy the mission as conditions change? | A graph of possible mission threads | The complete institutional enterprise needed to field and govern those paths |
| JADC2 | How does the Joint Force improve command and control across domains, echelons, organizations, and functions? | The joint command-and-control enterprise | A single product, network, or automatic engagement loop |
| CJADC2 | How does that enterprise include allied and other international mission partners? | The combined and joint enterprise | Automatic release of data, shared national authority, or identical partner systems |
Research basis: KW-RPT-007, KW-RPT-013, KW-RPT-014, and KW-RPT-041.
The JADC2 enterprise stack
JADC2 works only when several layers mature together. Building one layer while ignoring the others creates a connected demonstration rather than a durable command-and-control capability.
| Layer | Required capability | Common failure if treated alone |
|---|---|---|
| Mission and command | Intent, priorities, decision rights, delegated authorities, control measures, exception handling, and accountability | Software recommends a technically attractive option that no responsible authority may use |
| Data | Discoverable data products with shared semantics, source identity, time, confidence, provenance, sensitivity, permitted use, and quality | Systems exchange messages but interpret the same fields differently |
| Transport | Diverse tactical links, terrestrial and satellite paths, store-and-forward services, gateways, and priority management | One gateway, waveform, or long-haul path becomes a hidden single point of failure |
| Compute | Platform, tactical-edge, regional, and enterprise processing placed according to latency, connectivity, security, and resilience needs | A time-critical function waits for a distant cloud or central headquarters |
| Applications | Role-tailored command tools, fusion, planning, decision support, logistics, protection, and assessment services | Every organization receives another disconnected dashboard |
| Trust and security | Identity, device and workload trust, zero-trust policy, cryptographic provenance, supply-chain integrity, segmentation, and recovery | A compromised but connected node propagates plausible false state |
| People and process | Doctrine, training, tactics, staffing, data stewardship, mission engineering, and realistic exercises | Technology exists but organizations do not know when or how to use it |
| Partners | Federated identity, semantic agreements, releasability, national caveats, cross-domain controls, and combined procedures | A “joint” solution fails when the mission becomes combined |
Research basis: KW-RPT-007, KW-RPT-038, KW-RPT-042, KW-RPT-044, and KW-RPT-046.
How a composable JADC2 mission thread works
The following synthetic sequence shows the enterprise responsibilities around a kill-web path. It is intentionally abstract and does not model a real target, platform, weapon, location, or operational rule.
-
01
Publish a qualified observation
A source produces an observation with identity, time, uncertainty, provenance, sensitivity, permitted use, and health metadata.
-
02
Translate without erasing meaning
Gateways and adapters map syntax and semantics while preserving the original record and documenting transformations.
-
03
Build a shared but role-tailored state
Fusion and data services make an underlying state discoverable while each authorized role receives only the detail it needs and may receive.
-
04
Generate bounded options
Decision-support services identify possible combinations of sensing, transport, command, support, and effect capabilities.
-
05
Apply independent gates
Compatibility, trust, freshness, capacity, releasability, safety, policy, and authority checks remove impermissible options before ranking.
-
06
Authorize and execute
A responsible authority selects, modifies, defers, or rejects the option; the assigned organization executes only inside the authorized bounds.
-
07
Assess and reconcile
The enterprise records the result, updates state, resolves conflicting records, revalidates authority, and preserves the complete decision provenance.
Public service contributions to the wider enterprise
Publicly described service efforts are contributions to the joint and combined enterprise, not independent replacements for it. Names, organizations, and implementation details continue to evolve, so the table should be read as a current public orientation rather than a fielding-status claim.
| Organization | Public contribution | Joint or combined dependency |
|---|---|---|
| Department of the Air Force | The DAF Battle Network and the Advanced Battle Management System lineage focus on connecting sensing, decision, and command capabilities through a system-of-systems approach. | Interfaces, data products, transport, authorities, and mission applications must work beyond Air Force boundaries. |
| Army | Next Generation Command and Control and Project Convergence use iterative experimentation to integrate transport, infrastructure, data, and applications for formations and joint partners. | Army operational data and applications must remain interoperable with joint, intelligence, coalition, and other-service systems. |
| Navy | Project Overmatch develops the naval contribution to the wider command-and-control enterprise and has included partner integration work. | Maritime forces must exchange trusted data while operating at distance, under intermittent transport, and within combined task groups. |
| Marine Corps | Project Dynamis and related force-design efforts accelerate Marine contributions to CJADC2, including integration with naval and joint pathways. | Low-signature, mobile, expeditionary nodes must remain useful without becoming dependent on continuous high-bandwidth reachback. |
| Space Force and space organizations | Warning, tracking, communications transport, position-navigation-timing, and space-domain awareness support global and theater mission threads. | Space services must connect to terrestrial command processes while avoiding common-mode dependence on one constellation, ground segment, or data path. |
| Joint Staff, combatant commands, defense agencies, and intelligence organizations | Reference architecture, reference design, capability requirements, data-sharing experiments, mission-partner arrangements, and command procedures provide enterprise integration. | No service contribution becomes truly joint or combined until it works in end-to-end mission threads under realistic authorities and degradation. |
Research basis: KW-RPT-007, KW-RPT-013, KW-RPT-038, and KW-RPT-044. Current public program names should be rechecked at each editorial review.
Why the “Combined” in CJADC2 matters
International partners do not become interchangeable nodes merely because their systems can connect. They may have different authorities, data standards, classification regimes, national caveats, operational priorities, trust anchors, acquisition histories, and disclosure obligations.
Combined operations therefore add policy and accountability to every data product and every possible edge. A partner may be allowed to receive a minimized track but not the raw source. It may be allowed to use information for awareness but not for another purpose. It may provide sensing without transferring engagement authority. Those distinctions must survive translation, caching, derivation, disconnection, and later revocation.
Releasability
What may be disclosed, at what level of detail, to which receiving organization, and for how long?
Permitted use
May the recipient display, fuse, retain, retrain, redistribute, or act on the data?
National caveats
Which missions, actions, locations, or conditions remain outside a partner’s authorization?
Revocation and lineage
When a source is corrected or access is withdrawn, which derived products and downstream decisions must be reconsidered?
Research basis: KW-RPT-007 and KW-RPT-042.
Interoperability has more than one layer
| Layer | Question | Unsafe shortcut |
|---|---|---|
| Connectivity | Can the nodes exchange a message through an available path? | The link is up, therefore the mission can proceed. |
| Syntax | Can the recipient parse the message structure and fields? | The packet decoded, therefore both systems mean the same thing. |
| Semantics | Do producers and consumers interpret identity, time, location, status, confidence, and relationships consistently? | The field names match, therefore the operational meaning matches. |
| Trust | Are identity, source, transformation, software, and data integrity sufficiently verified? | A known sender guarantees true or uncorrupted data. |
| Releasability and permitted use | May this recipient receive and use this information for this purpose? | Access implies unrestricted reuse. |
| Authority | Does the responsible institution possess current authority for the proposed decision or task? | Technical capability creates permission. |
| Timing and quality | Is the information current and accurate enough for the decision window? | A valid old record remains valid for a new decision. |
JADC2 must work while the environment is degraded
A command-and-control enterprise designed only for an intact network and trusted data is not resilient. Contested operation should be treated as the normal test environment, not an exceptional demonstration mode.
- Disconnected, disrupted or denied, intermittent, and low-bandwidth transport.
- Electronic attack, cyber compromise, spoofing, congestion, and traffic-priority conflicts.
- Loss or degradation of position, navigation, timing, and trusted time.
- Stale observations, delayed acknowledgments, inconsistent state, and competing versions of the operating picture.
- Compromised nodes, invalid software or model updates, and uncertain supply-chain state.
- Loss of a regional cloud, gateway, identity service, authority service, or other shared dependency.
- Coalition disconnection followed by reconciliation without silently expanding authority.
- Operator overload and inadequate time for meaningful review.
Local continuity
Time-sensitive and safety-critical functions continue locally only inside predeclared evidence and authority bounds.
Graceful degradation
The enterprise reduces function, raises uncertainty, or holds instead of pretending that lost inputs remain valid.
Quarantine
Untrusted nodes, data, models, or configurations are contained without allowing their state to propagate.
Reconciliation
Reconnected partitions compare histories, resolve duplicate ownership, preserve conflicts, and revalidate authority before resuming broader operation.
Research basis: KW-RPT-004, KW-RPT-011, KW-RPT-041, KW-RPT-044, and KW-RPT-046.
Machine-speed information does not erase human authority
JADC2 can accelerate discovery, translation, fusion, comparison, routing, and coordination. Those functions can narrow a decision window, but they do not convert a model recommendation into legal or command authority. The system must represent who may decide, what has been delegated, when that delegation expires, what evidence is required, what actions remain prohibited, and who receives control when conditions fail.
Meaningful human judgment cannot be inferred from the existence of an approval button. A reviewer needs sufficient time, access to evidence and contrary information, competence, actual authority, and a practical ability to pause, reject, alter, or defer. When the system acts faster than detailed review is possible, the prior institutional delegation, runtime bounds, machine evidence, and post-event reconstruction become even more important.
Research basis: KW-RPT-012, KW-RPT-039, KW-RPT-040, and KW-RPT-049.
The hardest problem is enterprise governance
Platform programs are usually accountable for the cost, schedule, performance, and readiness of bounded systems. JADC2 value emerges across many programs, interfaces, data services, networks, applications, authorities, and organizations. That means the unit of acquisition accountability can be smaller than the unit of operational value.
The enterprise therefore needs mission-thread owners, interface governance, data-product stewardship, common test environments, software and data rights, persistent product teams, portfolio investment decisions, independent evaluation, and mechanisms for retiring duplicative or incompatible efforts. Local success should not be counted as joint progress unless it improves an end-to-end mission thread.
- Fund interfaces, data products, identity, gateways, test environments, and integration—not only platforms.
- Treat open interfaces and conformance evidence as first-class deliverables.
- Separate relatively stable safety-critical layers from rapidly changing mission applications where feasible.
- Measure cross-service and combined mission outcomes rather than counting demonstrations or connected endpoints.
- Preserve software, configuration, model, policy, and authority provenance so later changes invalidate the correct evidence.
- Create a comprehensive framework for responsibilities, investments, milestones, and lessons across the enterprise.
Research basis: KW-RPT-005, KW-RPT-010, and KW-RPT-038.
Measures that reveal whether the enterprise actually works
| Measure | What it reveals | What a weak metric may hide |
|---|---|---|
| Mission-thread completion under disruption | Whether an end-to-end outcome remains possible after defined node, link, data, or service failures | A laboratory connection that works only in the baseline state |
| Decision quality and time | Whether users receive usable evidence and options within the relevant window | Fast delivery of incomplete or misleading information |
| Data age and provenance completeness | Whether the decision used current, traceable records | A common picture built from stale or unexplained data |
| Independent path diversity | Whether alternates avoid shared failure causes | Several routes that depend on the same gateway, cloud, clock, or software lineage |
| Authority correctness | Whether tasking stayed inside current delegation, scope, and expiry | Technically successful but unauthorized execution |
| Combined interoperability | Whether partners can exchange and use appropriately minimized information under caveats | A U.S.-only demonstration labeled combined |
| Recovery and reconciliation time | How quickly the enterprise contains faults, compares histories, and returns to a trustworthy state | Rapid reconnection that preserves conflicting or poisoned state |
| Decision-provenance completeness | Whether investigators can reconstruct evidence, transformations, software, models, authority, human information, action, and outcome | An event log that records only the final click or command |
| Integration cycle time | How quickly a new conforming capability can be tested and added without bespoke reintegration | A nominal open architecture that still depends on one incumbent |
Current official public source map
The public JADC2 record is distributed across enterprise strategy, independent oversight, and service-specific implementation updates. No one page proves that the complete combined enterprise is fielded or that every mission thread performs as intended. KillWebs.com therefore keeps source purpose and source limitation visible together.
| Source record | What it contributes | What it cannot prove by itself |
|---|---|---|
| KW-SRC-002 — DoD JADC2 Strategy | The original public Joint All-Domain Command and Control definition, sense–make sense–act framework, resilience, data, authorities, people, and mission partners. | Current implementation status, classified architecture, or end-to-end mission performance. |
| KW-SRC-006 — GAO oversight | Independent findings about enterprise framework, investment visibility, progress measures, responsibilities, and lesson sharing. | Classified performance or the current state of every component program. |
| KW-SRC-012 — CDAO CJADC2 | Current Combined Joint All Domain Command and Control terminology and the decision-advantage framing. | One bounded product, one acquisition baseline, or completed enterprise integration. |
| KW-SRC-013 — DAF Battle Network | The Department of the Air Force contribution and system-of-systems integration direction. | Joint acceptance merely because an Air Force pathway connects in one demonstration. |
| KW-SRC-014 — Army NGC2 | The Army full-stack combination of applications, data and AI, infrastructure, and transport under degraded conditions. | Enterprise-wide operational acceptance from one exercise or formation. |
| KW-SRC-015 — Navy Project Overmatch | The Navy contribution, resilient communications, autonomous operations, and Five Eyes collaboration. | Complete combined data-sharing controls or fielding scale. |
| KW-SRC-016 — Marine Project Dynamis | The Marine Corps contribution to CJADC2 and its relationship with the naval ecosystem. | Delivered capability or operational effectiveness from an initiative announcement. |
| KW-SRC-017 — Space architecture | Public space transport, tracking, battle-management, navigation, custody, and ground-layer contributions. | That every layer and tranche is deployed, accepted, and available to every mission thread. |
Open the curated Source Library for the current links, publishers, report routing, and limitations associated with KW-SRC-002, KW-SRC-006, and KW-SRC-012 through KW-SRC-017.
What KillWebs.com can safely demonstrate
KillWebs.com uses fixed fictional nodes, synthetic records, abstract roles, and non-operational outcomes to teach JADC2 architecture and governance. It can show how data quality, trust, compatibility, authority, human judgment, failure, and recovery change a mission thread without exposing or calculating a real operational pathway.
- No real targets, coordinates, weapon parameters, force dispositions, rules of engagement, or operational data.
- No live sensor, command, military, coalition, or Evulgare integration.
- No target ranking, weapon-target assignment, or force authorization.
- No claim that a synthetic scenario proves operational readiness, legal compliance, safety, or certification.
- No public exposure of private `.uai` memory, credentials, restricted reports, or unpublished evidence.
- Real-system integration, provenance, machine answerability, and failure reconstruction belong in a separately governed Evulgare project.