Observation source
Produces a fictional observation with time, uncertainty, health, and provenance.
observationJoint All-Domain Command and Control
JADC2 Mission-Thread Convergence Lab
JADC2 stands for Joint All-Domain Command and Control. CJADC2 stands for Combined Joint All-Domain Command and Control. This fixed public lab shows why a mission thread must pass independent technical, semantic, trust, partner, purpose, capacity, authority, human-review, assessment, and reconciliation conditions before it becomes usable.
Convergence, not mere connectivity
A route can exist and still be unusable.
A candidate thread becomes usable only when the data can move, be parsed, retain equivalent meaning, carry trustworthy provenance, remain fresh, satisfy uncertainty and quality conditions, comply with sensitivity and permitted-use limits, fit capacity and timing, remain inside current authority, receive meaningful human review where required, and preserve assessment and reconciliation.
Potential→Connected→Compatible→Trusted→Releasable→Authorized→Usable
Eight-stage model
Every stage remains visible—even when another thread succeeds.
- JSTAGE-01
Mission need and declared purpose
State the fictional need, intended outcome, scope, and prohibited uses.
- JSTAGE-02
Observation and evidence qualification
Inspect source, uncertainty, contradiction, age, and evidence quality.
- JSTAGE-03
Semantic translation and data-product construction
Make syntax and meaning explicit and preserve transformation loss.
- JSTAGE-04
Trust, provenance, freshness, and integrity checks
Verify identity, lineage, timing, health, and data integrity.
- JSTAGE-05
Releasability, permitted use, and partner checks
Apply minimization, sensitivity, releasability, and purpose limits.
- JSTAGE-06
Feasibility, capacity, timing, and dependency checks
Confirm transport, capacity, timing, availability, and independent path diversity.
- JSTAGE-07
Authority, human judgment, and action boundary
Check current delegation and meaningful review before bounded support.
- JSTAGE-08
Assessment, reconciliation, provenance, and return of control
Assess outcome, preserve history, reconcile state, and return control.
Abstract system roles
Eighteen fixed roles, not real platforms.
The catalog uses neutral service roles so the lesson applies to disaster response, infrastructure protection, logistics, cyber defense, evacuation support, combined awareness, and time-critical protective support.
Local preprocessing service
Filters and packages observations without erasing source lineage.
preprocessingTrusted-time service
Supplies bounded timing and synchronization evidence.
timeProvenance service
Preserves origin, custody, transformations, and dependency lineage.
provenanceSemantic translator
Converts declared schemas while recording information loss and version state.
translationData-product publisher
Publishes a minimized, purpose-bound fictional data product.
publisherPrimary transport path
Carries a bounded data product over the preferred fictional route.
transportIndependent alternate transport
Provides a separately governed alternate route with a distinct failure domain.
transportEdge compute service
Performs bounded local processing during degraded connectivity.
computeFusion and state-estimation service
Maintains a qualified fictional state while preserving disagreement.
fusionContrary-evidence service
Surfaces contradictory or missing evidence before option comparison.
evidenceDecision-support service
Compares already permissible support options without creating command authority.
decision-supportHuman command role
Exercises accountable judgment with evidence, time, competence, and intervention power.
human-commandAuthority gate
Checks declared purpose, scope, expiry, revocation, and prohibited actions.
authorityMission-partner release gate
Applies releasability, minimization, purpose, and downstream-use constraints.
partner-releaseBounded task coordinator
Coordinates an approved non-force support task inside declared limits.
coordinationNon-force effect or support role
Performs a fictional support, protection, recovery, evacuation, or cyber-defense action.
supportAssessment, audit, and reconciliation service
Records outcome, reconciles state, preserves history, and returns control.
assessmentShow the 24 fixed candidate relationships
| ID | From | To | Relationship | Failure domain |
|---|---|---|---|---|
| JREL-01 | JROLE-01 | JROLE-02 | observation-feed | source-domain |
| JREL-02 | JROLE-03 | JROLE-02 | trusted-time | time-domain |
| JREL-03 | JROLE-02 | JROLE-04 | provenance-append | provenance-domain |
| JREL-04 | JROLE-04 | JROLE-06 | lineage-envelope | provenance-domain |
| JREL-05 | JROLE-02 | JROLE-05 | schema-input | gateway-domain |
| JREL-06 | JROLE-05 | JROLE-06 | translated-product | gateway-domain |
| JREL-07 | JROLE-06 | JROLE-07 | primary-publish | transport-primary |
| JREL-08 | JROLE-06 | JROLE-08 | alternate-publish | transport-alternate |
| JREL-09 | JROLE-07 | JROLE-09 | primary-delivery | transport-primary |
| JREL-10 | JROLE-08 | JROLE-09 | alternate-delivery | transport-alternate |
| JREL-11 | JROLE-09 | JROLE-10 | edge-state | compute-domain |
| JREL-12 | JROLE-10 | JROLE-11 | hypothesis-check | evidence-domain |
| JREL-13 | JROLE-11 | JROLE-12 | contrary-evidence | evidence-domain |
| JREL-14 | JROLE-10 | JROLE-12 | qualified-state | compute-domain |
| JREL-15 | JROLE-12 | JROLE-15 | partner-check | partner-domain |
| JREL-16 | JROLE-12 | JROLE-14 | authority-request | authority-domain |
| JREL-17 | JROLE-15 | JROLE-14 | release-result | partner-domain |
| JREL-18 | JROLE-14 | JROLE-13 | review-package | authority-domain |
| JREL-19 | JROLE-13 | JROLE-16 | approved-support-task | human-command-domain |
| JREL-20 | JROLE-16 | JROLE-17 | bounded-coordination | coordination-domain |
| JREL-21 | JROLE-17 | JROLE-18 | outcome-evidence | support-domain |
| JREL-22 | JROLE-18 | JROLE-10 | reconciled-state | reconciliation-domain |
| JREL-23 | JROLE-18 | JROLE-14 | authority-status-feedback | reconciliation-domain |
| JREL-24 | JROLE-18 | JROLE-13 | return-of-control | human-command-domain |
Six immutable teaching scenarios
Command and control is broader than one sensor-to-shooter pattern.
Joint disaster-response sensing and communications restoration
Three fictional organizations share qualified observations and coordinate communications restoration and evacuation support.
Non-force emergency supportDistributed infrastructure protection under transport degradation
Abstract monitoring services coordinate inspection and restoration of fictional infrastructure under degraded transport.
Protection and recoveryCoalition maritime awareness with a releasability caveat
All candidate threads require a fictional mission-partner release gate and purpose-limited data product.
Combined awarenessLogistics rerouting after loss of a shared gateway
Candidate threads coordinate fictional supply status after a shared gateway or transport failure.
Sustainment coordinationCyber-defense coordination with contradictory evidence and a compromised service
A fictional cyber-defense workflow preserves contradictory evidence and quarantines a suspect processing service.
Defensive cyber coordinationAbstract time-critical defense support with a separate force boundary
Machine-speed services compare protective support threads, but the fixed public model cannot select a target, assign a weapon, or authorize force.
Time-critical protective supportFixed synthetic analysis
Which candidate threads converge—and where do the others hold?
No target, weapon, force, legal, certification, or deployment determination is made.
joint-disaster-response
Non-force emergency support
Joint disaster-response sensing and communications restoration
Three fictional organizations share qualified observations and coordinate communications restoration and evacuation support.
- Declared purpose
- Restore communications and route evacuation-support information without modeling a real location or organization.
- Scope
- Public synthetic support thread only.
- Applied condition
- Evaluate the fixed baseline exactly as declared.
Current overall posture
Mission thread usable within declared bounds
The fixed scenario is classified as “Mission thread usable within declared bounds.” At least one candidate thread satisfies every declared technical, semantic, trust, partner, purpose, capacity, authority, human-review, assessment, and reconciliation condition. A shorter or connected route is not automatically compatible, trusted, releasable, authorized, or usable.
Warnings
- At least one dependency or failure domain is shared across candidate threads; route count alone is not independent resilience.
- The lab evaluates public synthetic convergence only. It does not select targets, assign weapons, recommend engagement, authorize force, or prove readiness.
Mandatory holds
- No additional thread hold.
Next actions
- Use the selected fictional thread only within its declared non-force support purpose.
- Keep every held or rejected alternative visible for review and recovery planning.
- Preserve evidence, authority state, transformation history, and residual unknowns through assessment.
- Return control rather than silently expanding scope when the fixed condition cannot be satisfied.
Residual unknowns
- Real emergency conditions, legal authorities, and partner agreements are not represented.
- The catalog does not represent real organizations, systems, authorities, partner agreements, operational performance, targets, weapons, or deployment evidence.
- A synthetic posture is not operational acceptance, legal review, certification, command authority, or permission to apply force.
Candidate-thread comparison
| Thread | Posture | Connected | Compatible | Trusted | Releasable | Authorized | Usable |
|---|---|---|---|---|---|---|---|
| JTHREAD-DR-01Primary restoration thread | Pass Mission thread usable within declared bounds | Yes | Yes | Yes | Yes | Yes | Yes |
| JTHREAD-DR-02Independent alternate restoration thread | Pass Mission thread usable within declared bounds | Yes | Yes | Yes | Yes | Yes | Yes |
| JTHREAD-DR-03Partner-minimized awareness thread | Pass Mission thread usable within declared bounds | Yes | Yes | Yes | Yes | Yes | Yes |
Stage-by-stage ledger
| Thread | Stage | Status | Finding |
|---|---|---|---|
| Primary restoration thread | JSTAGE-01 | Pass | Declared purpose and scope remain represented. |
| Primary restoration thread | JSTAGE-02 | Pass | Observation quality, uncertainty, and contrary evidence remain visible. |
| Primary restoration thread | JSTAGE-03 | Pass | Syntax and semantics must both be understood. |
| Primary restoration thread | JSTAGE-04 | Pass | Identity, provenance, freshness, and integrity are checked independently. |
| Primary restoration thread | JSTAGE-05 | Pass | Release and downstream use must both remain permitted. |
| Primary restoration thread | JSTAGE-06 | Pass | Reachability, capacity, and independent failure paths remain separate. |
| Primary restoration thread | JSTAGE-07 | Pass | Current authority and meaningful human review are required for bounded action. |
| Primary restoration thread | JSTAGE-08 | Pass | Outcome, history, reconciliation, and return of control remain open until completed. |
| Independent alternate restoration thread | JSTAGE-01 | Pass | Declared purpose and scope remain represented. |
| Independent alternate restoration thread | JSTAGE-02 | Pass | Observation quality, uncertainty, and contrary evidence remain visible. |
| Independent alternate restoration thread | JSTAGE-03 | Pass | Syntax and semantics must both be understood. |
| Independent alternate restoration thread | JSTAGE-04 | Pass | Identity, provenance, freshness, and integrity are checked independently. |
| Independent alternate restoration thread | JSTAGE-05 | Pass | Release and downstream use must both remain permitted. |
| Independent alternate restoration thread | JSTAGE-06 | Pass | Reachability, capacity, and independent failure paths remain separate. |
| Independent alternate restoration thread | JSTAGE-07 | Pass | Current authority and meaningful human review are required for bounded action. |
| Independent alternate restoration thread | JSTAGE-08 | Pass | Outcome, history, reconciliation, and return of control remain open until completed. |
| Partner-minimized awareness thread | JSTAGE-01 | Pass | Declared purpose and scope remain represented. |
| Partner-minimized awareness thread | JSTAGE-02 | Pass | Observation quality, uncertainty, and contrary evidence remain visible. |
| Partner-minimized awareness thread | JSTAGE-03 | Pass | Syntax and semantics must both be understood. |
| Partner-minimized awareness thread | JSTAGE-04 | Pass | Identity, provenance, freshness, and integrity are checked independently. |
| Partner-minimized awareness thread | JSTAGE-05 | Pass | Release and downstream use must both remain permitted. |
| Partner-minimized awareness thread | JSTAGE-06 | Pass | Reachability, capacity, and independent failure paths remain separate. |
| Partner-minimized awareness thread | JSTAGE-07 | Pass | Current authority and meaningful human review are required for bounded action. |
| Partner-minimized awareness thread | JSTAGE-08 | Pass | Outcome, history, reconciliation, and return of control remain open until completed. |
Twelve independent convergence dimensions
| ID | Dimension | Status | Declared result | Finding |
|---|---|---|---|---|
| JCONV-01 | Technical reachability | Pass | 3 of 3 candidate threads satisfy the declared condition | All candidate threads satisfy this dimension. |
| JCONV-02 | Interface and syntax compatibility | Pass | 3 of 3 candidate threads satisfy the declared condition | All candidate threads satisfy this dimension. |
| JCONV-03 | Semantic compatibility | Pass | 3 of 3 candidate threads satisfy the declared condition | All candidate threads satisfy this dimension. |
| JCONV-04 | Identity and workload trust | Pass | 3 of 3 candidate threads satisfy the declared condition | All candidate threads satisfy this dimension. |
| JCONV-05 | Evidence provenance and integrity | Pass | 3 of 3 candidate threads satisfy the declared condition | All candidate threads satisfy this dimension. |
| JCONV-06 | Freshness, timing, and synchronization | Pass | 3 of 3 candidate threads satisfy the declared condition | All candidate threads satisfy this dimension. |
| JCONV-07 | Data quality and uncertainty | Pass | 3 of 3 candidate threads satisfy the declared condition | All candidate threads satisfy this dimension. |
| JCONV-08 | Sensitivity, releasability, and minimization | Pass | 3 of 3 candidate threads satisfy the declared condition | All candidate threads satisfy this dimension. |
| JCONV-09 | Permitted purpose and downstream-use limits | Pass | 3 of 3 candidate threads satisfy the declared condition | All candidate threads satisfy this dimension. |
| JCONV-10 | Capacity, availability, and independent path diversity | Pass | 3 of 3 candidate threads satisfy the declared condition | All candidate threads satisfy this dimension. |
| JCONV-11 | Delegated authority, expiry, revocation, and human review | Pass | 3 of 3 candidate threads satisfy the declared condition | All candidate threads satisfy this dimension. |
| JCONV-12 | Assessment, audit, reconciliation, and residual unknowns | Pass | 3 of 3 candidate threads satisfy the declared condition | All candidate threads satisfy this dimension. |
Data products and permitted use
| ID | Product | Purpose | Sensitivity | Permitted use |
|---|---|---|---|---|
| JDP-DR-01 | Synthetic outage observation | Communications restoration awareness | public-synthetic | declared scenario only |
| JDP-DR-02 | Minimized evacuation-support product | Evacuation coordination | partner-shareable | evacuation support only |
Trust and provenance
| Thread | Identity | Provenance | Timing | Data quality |
|---|---|---|---|---|
| Primary restoration thread | Yes | Yes | Yes | Yes |
| Independent alternate restoration thread | Yes | Yes | Yes | Yes |
| Partner-minimized awareness thread | Yes | Yes | Yes | Yes |
Authority and human review
| Thread | Releasable | Purpose | Authority | Meaningful review | Action boundary |
|---|---|---|---|---|---|
| Primary restoration thread | Yes | Yes | Yes | Yes | Continue bounded support |
| Independent alternate restoration thread | Yes | Yes | Yes | Yes | Continue bounded support |
| Partner-minimized awareness thread | Yes | Yes | Yes | Yes | Continue bounded support |
Shared dependencies and common mode
| Thread | Failure domains | Shared domains | Independent |
|---|---|---|---|
| Primary restoration thread | transport-primary, compute-alpha, authority-alpha | authority-alpha | Yes |
| Independent alternate restoration thread | transport-alternate, gateway-beta, authority-alpha | transport-alternate, authority-alpha | Yes |
| Partner-minimized awareness thread | transport-alternate, partner-release, authority-alpha | transport-alternate, authority-alpha | Yes |
No composite score is calculated. No composite JADC2, interoperability, mission-thread, readiness, trust, authority, confidence, safety, legality, operational-acceptance, or certification score is calculated.
Fourteen required distinctions
Convergence cannot be compressed into one green light.
Connectedcompatible
Compatiblesemantically equivalent
Known identitytrustworthy evidence
Trusted sendertrue data
Data accesspermission to reuse data
Releasable dataauthorized action
Available resourceauthority to consume it
Priority labelinstitutional precedence
Alternative routeindependent failure path
Machine recommendationcommand decision
Human clickmeaningful human judgment
Connection restoredauthority restored
Successful technical executionauthorized or legitimate execution
Synthetic convergence postureoperational acceptance, certification, or force authorization
Public and operational boundary
This lab explains governed mission threads. It does not operate one.
Only allowlisted fictional scenario and change identifiers are accepted. The lab contains no real country, organization, service, platform, sensor, weapon, target, person, location, coordinate, range, waveform, authority instrument, partner agreement, classified data, operational threshold, or live source.
- Never calculated
- Target quality, target ranking, weapon-target assignment, engagement recommendation, probability of kill, casualty estimate, force optimization, mission-success prediction, legality, readiness, or certification.
- Never connected
- Operational systems, Evulgare APIs, KillChains APIs, external feeds, accounts, evidence stores, WebSockets, background sync, or server-side user state.
- Allowed outputs
- Observe, translate, minimize, corroborate, compare, route to review, continue bounded support, degrade, quarantine, reconcile, hold, or return control.
- Standing rule
- Connectivity, recommendation, technical success, and a human click do not create authority or permission to apply force.
Direct answers
JADC2 mission-thread FAQ
What does JADC2 stand for?
JADC2 stands for Joint All-Domain Command and Control. It is the wider joint enterprise that enables, secures, governs, tests, and sustains mission threads across domains and organizations.
What does CJADC2 stand for?
CJADC2 stands for Combined Joint All-Domain Command and Control. Combined makes international mission-partner integration explicit without implying automatic data release or shared national authority.
What is mission-thread convergence?
It is the process by which a potential route becomes progressively connected, compatible, semantically understandable, trusted, releasable, purpose-permitted, feasible, authorized, reviewable, assessable, and reconcilable.
Does a connected thread become authorized automatically?
No. Reachability is only one condition. Compatibility, evidence, trust, releasability, purpose, capacity, authority, meaningful human judgment, assessment, and reconciliation remain independent gates.
Does this lab choose a target or assign a weapon?
No. It uses fixed fictional non-force and protective support scenarios and cannot select targets, rank targets, assign weapons, recommend engagement, authorize force, or plan a real operation.
Does a synthetic usable posture prove operational readiness?
No. A posture describes only the declared fictional catalog. It is not operational acceptance, legal review, safety evidence, certification, command authority, or deployment approval.