Skip to content
Article reader Listen + reading controls
LISTEN + READ YOUR WAY

Article reader

Preparing the reader…

0:00 0:00
Reading settings
Text size
100%

A CJADC2 Capability Is Not Viable Until the Mission Can Reach It

In January 2024, the Pentagon’s declaration that GIDE 8 had produced a minimum viable capability for Combined Joint All-Domain Command and Control (CJADC2) represented real progress. The caveat was equally important: the capability was not yet fully accessible across the force.

That tension reveals a problem in how large institutions use the language of product development. “Minimum viable capability” can sound like a modest version of a future system—a technical baseline with enough features to demonstrate direction. In a mission environment, however, viability cannot be separated from reach. A capability that exists but cannot be reliably accessed, understood, authorized, and employed by its intended users remains an integration result, not an operational result.

The Department’s announcement for GIDE 8 described a minimum viable capability aligned to two mission threads: global integration and joint fires. The experiment brought together the services, combatant commands, Joint Staff, and international partners, and it sought to field initial capabilities while refining concepts, tactics, techniques, procedures, and policy.

Those are appropriate goals. The harder question is what evidence should justify the word capability.

From Minimum Viable Product to Minimum Viable Capability

The concept of a minimum viable product emerged from commercial product development as a way to test assumptions with real users before making a larger investment. The word minimum limits scope; viable means useful enough to generate valid learning; product means a coherent experience for a customer.

In defense, substituting capability expands the obligation. The relevant object is not a software application. It is the ability of a force to achieve an operational effect through a combination of people, doctrine, organization, training, materiel, leadership, personnel, facilities, policy, data, and software.

For CJADC2, a minimum viable capability should therefore include at least:

  • a defined mission thread and decision outcome;
  • representative operational users with appropriate authorities;
  • data that is available, interpretable, timely, and releasable;
  • interoperable services and interfaces across participating organizations;
  • identity, access, and policy enforcement at the required classifications;
  • resilient behavior under latency, disconnection, and partial failure;
  • documented human decision rights and escalation paths;
  • training and support sufficient for meaningful employment;
  • observable performance and failure modes;
  • and an owner with funding and responsibility for the next increment.

This is a demanding definition by design. The Department does not need “minimum viable” to become a rhetorical substitute for “promising prototype.” It needs the term to bound a small but complete slice of operational value.

Accessibility Is a System Property

Accessibility in a joint and coalition environment is not a login-screen problem. It is the emergent result of multiple architectural and institutional conditions.

Network reach

The user must be able to reach the service from the operational environment, including at relevant classification levels and under degraded communications. A cloud-hosted capability may be globally available in theory and operationally unreachable at the edge.

Identity and authorization

The system must recognize users and services across organizational boundaries and decide what each may do. Static account provisioning is insufficient for dynamic coalitions. Attributes, mission roles, policy, and revocation must travel with the interaction.

Data entitlement and releasability

A user may access the application while remaining unable to see the evidence needed for a decision. Coalition viability depends on deliberate data segmentation, provenance, disclosure rules, and cross-domain patterns—not on hoping that information can be released after the workflow is designed.

Semantic accessibility

Data can be technically visible and operationally unintelligible. Different services and partners may use different identifiers, taxonomies, geospatial conventions, confidence scales, or definitions of status. Semantic mediation is part of access.

Cognitive accessibility

The interface must present information in a form that fits the user’s task, tempo, expertise, and decision authority. A dense common operating picture may expose more information while reducing understanding.

Organizational accessibility

Users require training, approved procedures, support, and permission to integrate the capability into real work. A system can clear every technical boundary and remain outside the actual decision process.

These layers explain why accessibility cannot be appended after a core capability is built. It is one of the capability’s defining characteristics.

Distribution Is Where Trust Becomes Concrete

CJADC2 depends on trust across organizations that do not share every system, policy, or risk assumption. The CDAO’s CJADC2 overview correctly notes that the construct is not a single system and that it must connect allied and partner command-and-control capabilities.

In that environment, trust must be represented in machine-enforceable and human-understandable forms:

  • Who produced this information?
  • Through which transformations did it pass?
  • How current is it?
  • What uncertainty and caveats apply?
  • Which policy authorizes its use?
  • Can the recipient propagate it or act on it?
  • What happens if a source later proves compromised?

These questions point toward a data-centric architecture in which provenance, policy, and semantics accompany the information. They also point toward zero-trust security: access decisions based on continuously evaluated identity, device, data, and context rather than location on a presumed trusted network. The DoD Zero Trust Strategy is therefore not adjacent to CJADC2. It is part of the mechanism through which joint access can scale without erasing necessary boundaries.

“Fully Accessible” Is Not the Same as “Available to Everyone”

The phrase can also mislead in the opposite direction. A mission capability should not expose all information and functions indiscriminately. Combined operations require differentiated access based on role, mission, authority, risk, and releasability.

The objective is coherent access, not universal access: each authorized participant can obtain the minimum sufficient information and functionality needed to contribute to the mission thread, while the system preserves security, provenance, and accountability.

That requires designing for coalition and cross-domain use from the beginning. Otherwise, U.S.-only workflows become the implicit reference architecture, and partner access is implemented as a diminished copy. The result may allow information sharing while preserving a decision hierarchy and latency that undermine the very advantage CJADC2 is intended to create.

A Better Readiness Model

Rather than asking whether the minimum viable capability has been “delivered,” leaders should assess readiness along several dimensions:

Dimension Minimum credible evidence
Mission utility A representative user completes a consequential mission thread better than the baseline process.
Reach Intended users can connect from representative environments and security domains.
Interoperability Participating systems exchange information without exercise-specific manual repair.
Comprehension Users interpret the information, uncertainty, and recommended actions correctly.
Resilience The workflow degrades safely when communications, data, models, or services fail.
Governance Decision rights, data responsibilities, model limitations, and incident paths are explicit.
Sustainment An accountable owner, funding, support model, and change pipeline exist.
Learning Telemetry and feedback reveal whether the capability improves decisions and where it fails.

A capability may be mature on one dimension and immature on another. That is not a reason to delay all use until perfection. It is a reason to constrain the scope of use explicitly and make the next learning objective visible.

What the Later Evidence Added

The January 2024 accessibility caveat described a transition in progress, not its endpoint. In August 2024, the Department’s Innovation Fact Sheet stated that the CJADC2 minimum viable capability had been fully funded and was actively used at U.S. Indo-Pacific Command, U.S. Central Command, and U.S. European Command.

That later development strengthens the original claim, but it does not eliminate the need for disciplined measurement. “In use” should lead to questions about mission frequency, user populations, operational outcomes, failure rates, partner participation, and the speed with which field evidence changes the product. A minimum viable capability is valuable not because it completes a program but because it begins a trustworthy learning relationship with the mission.

The Strategic Inference

The accessibility problem is not a final-mile inconvenience. It is a diagnostic of whether CJADC2 has been conceived as an integrated mission capability or as a collection of connected technologies.

If reach, identity, releasability, semantics, human comprehension, resilience, and organizational authority are treated as first-class design concerns, a small end-to-end capability can create real learning and expand deliberately. If they are deferred, technical progress accumulates behind boundaries that operators and partners must somehow cross later.

The right standard is straightforward: the minimum viable capability must be viable for the mission, not merely visible to the program.

This essay was substantially revised in July 2026. The update incorporates official information published after the original January 2024 commentary and distinguishes that later evidence from the historical claim.

For more on designing AI-enabled mission systems as complete socio-technical capabilities, see my work on AI engineering, knowledge infrastructure, and trustworthy operations.

References

READER-NEUTRAL SUBSCRIPTION

Follow Field Notes via RSS.

Copy this address into the RSS reader you already use. New notes will appear there automatically—no account, email address, or tracking required.

Open the feed