Event log
Joint All-Domain Command and Control evidence, invalidation, reconciliation, and fresh review
JADC2 Mission-Thread Evidence and Reconciliation Replay Lab
Replay six fixed fictional JADC2 and CJADC2 histories. See how sources, transformations, versions, trust, partner-use decisions, authority, human review, alternatives, assessment, and later changes shape what remains current—without confusing replay with validation or authority.
Research basis KW-RPT-007 KW-RPT-013 KW-RPT-040 KW-RPT-041 KW-RPT-042 KW-RPT-043 KW-RPT-044 KW-RPT-046 KW-RPT-047
The replay question
A restored connection does not restore evidence, trust, authority, or reconciled state.
JADC2 stands for Joint All-Domain Command and Control. CJADC2 stands for Combined Joint All-Domain Command and Control. A mission-thread replay reconstructs why one fictional path was selected, held, or rejected and what later changed.
The lab preserves the immutable original history and derives a separate current view. Corrected, stale, revoked, contradicted, suspended, and withdrawn records remain visible rather than being silently deleted or rewritten.
- Original history
- What the fixed fictional system recorded under the versions, evidence, purpose, authority, and review conditions at that time.
- Current view
- Which records remain current and which require invalidation, reconciliation, return of control, or fresh independent review.
- Authority rule
- Replayable history and restored transport cannot create current authority.
- Public boundary
- No real logs, evidence, organizations, systems, targets, weapons, missions, operations, or external handoffs.
Sixteen independent elements
Reconstruct the decision-producing thread, not merely its final event.
Every element remains independently visible because a complete event log cannot compensate for missing provenance, stale semantics, withdrawn purpose, expired authority, or ceremonial human review.
- R-01
Stable identifiers
Which history, event, thread, and data-product identifiers remain stable across replay?
- R-02
Source and collection state
Who or what created the source, when was it collected, and what was its original state?
- R-03
Provenance and custody
Can source custody and transfer be reconstructed without unexplained substitution?
- R-04
Transformation and minimization
What normalization, redaction, aggregation, and semantic translation changed the source?
- R-05
Versions
Which schema, software, model, configuration, and policy versions produced the original result?
- R-06
Evidence quality
What uncertainty, contrary evidence, missing evidence, and quality limits were visible?
- R-07
Identity and workload trust
Which identity and workload trust decisions were current at the decision time?
- R-08
Release and permitted purpose
Was the data releasable, minimized, and permitted for the exact declared purpose?
- R-09
Reachability and capacity
What transport, timing, capacity, and failure-domain conditions shaped the thread?
- R-10
Authority and expiry
What authority, delegation, expiry, revocation, and human-review conditions existed?
- R-11
Alternatives
Which candidate alternatives were selected, held, or rejected, and why?
- R-12
Machine output
What bounded recommendation or coordination output did the machine produce?
- R-13
Human action
What evidence, time, competence, authority, and intervention power did the human actually have?
- R-14
Assessment and outcome
What outcome, assessment, contradiction, and residual unknown were recorded?
- R-15
Later change
What source, schema, software, policy, partner-use, partition, authority, or assessment change occurred later?
- R-16
Current disposition
What must now be invalidated, reconciled, returned to human control, or independently re-reviewed?
Fourteen distinctions
Replay, reconciliation, and human review must not become authority theater.
The left-hand record may be useful. It is not equivalent to the stronger condition on the right.
Replayable history
Validated decision quality
Reconstruction can show what happened without proving that the underlying decision was correct, safe, lawful, or effective.Original record
Current valid record
A historically valid record may later be corrected, revoked, superseded, expired, or contradicted.Generated rationale
Supporting evidence
A fluent rationale is a derived artifact and cannot replace inspectable evidence and transformations.Evidence present
Evidence accurate
A preserved artifact can be stale, misattributed, incomplete, corrupted, or factually wrong.Missing evidence
Evidence that never existed
An unavailable expected artifact is different from an observation or review record that was never created.Source correction
Complete downstream invalidation
Every dependent transform, recommendation, review, action, and assessment must be identified and re-evaluated.Connection restored
Authority restored
Transport recovery cannot renew expired, revoked, or out-of-scope authority.Partition healed
State reconciled
Reconnected nodes may retain conflicting task ownership, versions, observations, or authority state.Trusted sender
Trustworthy evidence
An authenticated source can still be wrong, compromised, stale, or outside the evaluated context.Release once permitted
Currently permitted use
Partner use, purpose, sensitivity, or receiving-domain permission may later be withdrawn.Human acknowledgment
Independent human judgment
A click does not establish evidence access, time, competence, authority, alternatives, or practical intervention power.Technical rollback
Completed-consequence remedy
Restoring technical state does not reverse every institutional or physical consequence.Reconciliation complete
Force, legal, certification, or deployment authority
A coherent current state remains only a technical and evidentiary condition.Six immutable histories
Replay non-force mission-thread evidence across joint and combined support contexts.
Each history contains twelve fixed events and explicit dependencies. None represents an actual organization, operation, target, platform, weapon, location, or authority instrument.
Joint emergency support
Disaster-response information routing
A fictional multi-organization network routes infrastructure-damage observations to a bounded coordination service.
A source correction must propagate through routing and assessment rather than remain an isolated note.Critical infrastructure protection
Infrastructure-protection coordination
A fictional protective network coordinates sensor, maintenance, and service-continuity information without modeling force.
Software or schema change requires fresh review even when the original history is perfectly replayable.Combined information sharing
Mission-partner awareness and releasability
A fictional mission partner contributes a minimized awareness product under explicit releasability and purpose conditions.
Release once permitted does not create permanent or universal permission to reuse partner data.Contested logistics support
Logistics recovery after gateway loss
A fictional logistics thread reroutes status data after a gateway fails and later reconnects with divergent state.
Partition healing is not state reconciliation, and restored connectivity does not restore authority.Defensive cyber coordination
Cyber-defense interpretation with contradictory evidence
A fictional defensive system compares anomaly evidence and a benign explanation before recommending containment.
Contradictory assessment must reopen the original rationale rather than disappear behind a fluent explanation.Protective decision support
Time-critical protective support
A fictional protective thread operates under a short authority window and explicit human-review conditions.
A recorded human action cannot be treated as meaningful review when the interface state or intervention conditions are missing.Original posture
History coherent within declared bounds
Current replay posture
History coherent within declared bounds
The original posture was “History coherent within declared bounds.” After “No later material change,” the current posture is “History coherent within declared bounds.” 0 of 12 immutable events now carry a changed, suspended, withdrawn, contradicted, or review state.
Warnings
- Replay reconstructs a fixed fictional history. It does not validate decision quality, create authority, certify a system, authorize force, or approve deployment.
Mandatory holds
- No additional mandatory hold in this selected fictional state.
Reconciliation actions
- Preserve original and current state and perform reconciliation only when a declared change creates a state conflict.
Return of control
- Return control if evidence, trust, release, authority, human review, or reconciliation conditions become unsatisfied.
Fresh review
- No additional fresh review is triggered beyond the bounded original fictional review.
Residual unknowns
- The fixed record does not establish how any real JADC2 or CJADC2 implementation would perform.
- The fictional outcome does not establish legal, command, force, certification, or deployment authority.
- Unrecorded reasoning and counterfactual outcomes remain unknown.
| Event | Time | Role | Type | Event and evidence | Data product | Versions | Authority / human review | Original | Current |
|---|---|---|---|---|---|---|---|---|---|
| JMR-H1-E01 | T+00:00 | Fictional observation source Sense |
source | Source observation created A fictional aerial survey source records a blocked access corridor with declared uncertainty. available-with-declared-uncertainty |
JMR-H1-DP-01 |
collector-2.4.1observation-3.0collection-policy-4 |
not-applicable No human decision at collection |
current | current No later change affects this event. |
| JMR-H1-E02 | T+00:08 | Provenance and custody service Evidence |
custody | Custody and provenance registered The observation is transferred through a public-safety provenance ledger. custody-recorded |
JMR-H1-DP-01 |
provenance-ledger-1.9.0prov-envelope-2.2custody-policy-3 |
not-applicable Evidence steward reviews custody exception only |
current | current No later change affects this event. |
| JMR-H1-E03 | T+00:18 | Minimization and transformation service Data |
transform | Data minimized and transformed Location precision is minimized before joint distribution. derived-from-source |
JMR-H1-DP-02 |
transform-service-5.1.2semantic-profile-7.1minimization-policy-6 |
not-applicable No approval; deterministic bounded transform |
current | current No later change affects this event. |
| JMR-H1-E04 | T+00:27 | Semantic translation and version registry Interoperability |
version | Semantic and software versions locked The emergency-access schema and translation bundle are locked. version-attested |
JMR-H1-DP-02 |
translator-4.6.0mission-thread-schema-5.0compatibility-policy-5 |
not-applicable Configuration custodian attests declared versions |
current | current No later change affects this event. |
| JMR-H1-E05 | T+00:36 | Evidence qualification service Make sense |
evidence | Evidence and contrary evidence qualified A ground report supports the blockage while a delayed report challenges severity. qualified-with-contrary-record |
JMR-H1-DP-03 |
evidence-service-3.8.4evidence-contract-4.2evidence-policy-8 |
not-applicable Analyst records uncertainty and contrary evidence |
current | current No later change affects this event. |
| JMR-H1-E06 | T+00:45 | Identity and workload trust service Trust |
trust | Identity and workload trust evaluated The source identity and transformation workload are authenticated. trust-decision-current |
JMR-H1-DP-03 |
trust-engine-2.7.3trust-assertion-3.1zero-trust-policy-7 |
not-applicable Trust steward may hold but cannot create mission authority |
current | current No later change affects this event. |
| JMR-H1-E07 | T+00:54 | Release and permitted-use steward Governance |
release | Release and permitted purpose decided The minimized product is permitted for emergency-routing support. release-current-for-declared-purpose |
JMR-H1-DP-04 |
release-gate-3.4.2release-contract-6.0partner-use-policy-9 |
not-applicable Release steward approves only the declared fictional purpose |
current | current No later change affects this event. |
| JMR-H1-E08 | T+01:02 | Mission-thread path service Transport |
reachability | Reachability, timing, capacity, and failure domains checked Two abstract paths are compared for timing, capacity, and shared gateway risk. technical-state-current |
JMR-H1-THREAD-01 |
path-service-6.2.1thread-state-4.0capacity-policy-5 |
not-applicable Coordinator may nominate a route but cannot authorize consequence |
current | current No later change affects this event. |
| JMR-H1-E09 | T+01:10 | Delegated authority gate Authority |
authority | Delegated authority and expiry checked A fictional coordination authority is current for emergency support only. authority-record-current |
JMR-H1-THREAD-01 |
authority-gate-4.3.0delegation-contract-3.4authority-policy-12 |
active-within-declared-bounds Authority reviewer confirms scope, expiry, and revocation state |
current | current No later change affects this event. |
| JMR-H1-E10 | T+01:18 | Bounded option composer Decision support |
recommendation | Bounded machine coordination output produced The composer recommends continued collection and an alternate supply route. rationale-linked-to-evidence |
JMR-H1-THREAD-01 |
option-composer-5.5.0recommendation-contract-4.1coordination-policy-10 |
recommendation-only Machine output cannot authorize action |
current | current No later change affects this event. |
| JMR-H1-E11 | T+01:29 | Human merits reviewer Human judgment |
human-review | Human merits review recorded A qualified reviewer inspects evidence, uncertainty, and alternatives before confirming the bounded recommendation. review-record-complete |
JMR-H1-THREAD-01 |
review-console-3.6.8interface-state-2.9human-review-policy-11 |
reviewer-authorized-for-declared-decision Merits review with evidence access, time, competence, authority, and intervention power |
current | current No later change affects this event. |
| JMR-H1-E12 | T+02:05 | Assessment and reconciliation service Assessment |
assessment | Assessment and residual unknowns recorded Later field assessment records partial restoration and unresolved access uncertainty. assessment-current-with-residual-unknowns |
JMR-H1-ASSESS-01 |
assessment-service-2.8.2assessment-contract-3.3assessment-policy-6 |
no-new-authority-created Independent assessment role records outcome without rewriting history |
current | current No later change affects this event. |
| Event | Depends on | Dependency states | Records | Original | Current |
|---|---|---|---|---|---|
| JMR-H1-E01 | Origin event | No dependency | JMR-H1-REC-SOURCE | current | current |
| JMR-H1-E02 | JMR-H1-E01 | JMR-H1-E01: current | JMR-H1-REC-PROV | current | current |
| JMR-H1-E03 | JMR-H1-E02 | JMR-H1-E02: current | JMR-H1-REC-TRANSFORM | current | current |
| JMR-H1-E04 | JMR-H1-E03 | JMR-H1-E03: current | JMR-H1-REC-VERSION | current | current |
| JMR-H1-E05 | JMR-H1-E01, JMR-H1-E03, JMR-H1-E04 | JMR-H1-E01: current; JMR-H1-E03: current; JMR-H1-E04: current | JMR-H1-REC-EVIDENCE, JMR-H1-REC-CONTRARY | current | current |
| JMR-H1-E06 | JMR-H1-E02, JMR-H1-E04, JMR-H1-E05 | JMR-H1-E02: current; JMR-H1-E04: current; JMR-H1-E05: current | JMR-H1-REC-TRUST | current | current |
| JMR-H1-E07 | JMR-H1-E03, JMR-H1-E06 | JMR-H1-E03: current; JMR-H1-E06: current | JMR-H1-REC-RELEASE | current | current |
| JMR-H1-E08 | JMR-H1-E04, JMR-H1-E06, JMR-H1-E07 | JMR-H1-E04: current; JMR-H1-E06: current; JMR-H1-E07: current | JMR-H1-REC-PATH | current | current |
| JMR-H1-E09 | JMR-H1-E05, JMR-H1-E07, JMR-H1-E08 | JMR-H1-E05: current; JMR-H1-E07: current; JMR-H1-E08: current | JMR-H1-REC-AUTHORITY | current | current |
| JMR-H1-E10 | JMR-H1-E05, JMR-H1-E06, JMR-H1-E07, JMR-H1-E08, JMR-H1-E09 | JMR-H1-E05: current; JMR-H1-E06: current; JMR-H1-E07: current; JMR-H1-E08: current; JMR-H1-E09: current | JMR-H1-REC-RECOMMENDATION | current | current |
| JMR-H1-E11 | JMR-H1-E05, JMR-H1-E09, JMR-H1-E10 | JMR-H1-E05: current; JMR-H1-E09: current; JMR-H1-E10: current | JMR-H1-REC-INTERFACE, JMR-H1-REC-HUMAN | current | current |
| JMR-H1-E12 | JMR-H1-E10, JMR-H1-E11 | JMR-H1-E10: current; JMR-H1-E11: current | JMR-H1-REC-ASSESSMENT | current | current |
| Event | Type | Software | Schema | Policy | Authority | Evidence | Current state |
|---|---|---|---|---|---|---|---|
| JMR-H1-E01 | source | collector-2.4.1 | observation-3.0 | collection-policy-4 | not-applicable | available-with-declared-uncertainty | current |
| JMR-H1-E02 | custody | provenance-ledger-1.9.0 | prov-envelope-2.2 | custody-policy-3 | not-applicable | custody-recorded | current |
| JMR-H1-E03 | transform | transform-service-5.1.2 | semantic-profile-7.1 | minimization-policy-6 | not-applicable | derived-from-source | current |
| JMR-H1-E04 | version | translator-4.6.0 | mission-thread-schema-5.0 | compatibility-policy-5 | not-applicable | version-attested | current |
| JMR-H1-E05 | evidence | evidence-service-3.8.4 | evidence-contract-4.2 | evidence-policy-8 | not-applicable | qualified-with-contrary-record | current |
| JMR-H1-E06 | trust | trust-engine-2.7.3 | trust-assertion-3.1 | zero-trust-policy-7 | not-applicable | trust-decision-current | current |
| JMR-H1-E07 | release | release-gate-3.4.2 | release-contract-6.0 | partner-use-policy-9 | not-applicable | release-current-for-declared-purpose | current |
| JMR-H1-E08 | reachability | path-service-6.2.1 | thread-state-4.0 | capacity-policy-5 | not-applicable | technical-state-current | current |
| JMR-H1-E09 | authority | authority-gate-4.3.0 | delegation-contract-3.4 | authority-policy-12 | active-within-declared-bounds | authority-record-current | current |
| JMR-H1-E10 | recommendation | option-composer-5.5.0 | recommendation-contract-4.1 | coordination-policy-10 | recommendation-only | rationale-linked-to-evidence | current |
| JMR-H1-E11 | human-review | review-console-3.6.8 | interface-state-2.9 | human-review-policy-11 | reviewer-authorized-for-declared-decision | review-record-complete | current |
| JMR-H1-E12 | assessment | assessment-service-2.8.2 | assessment-contract-3.3 | assessment-policy-6 | no-new-authority-created | assessment-current-with-residual-unknowns | current |
| Event | Type | Data product | Evidence state | Description | Current state |
|---|---|---|---|---|---|
| JMR-H1-E01 | source | JMR-H1-DP-01 | available-with-declared-uncertainty | A fictional aerial survey source records a blocked access corridor with declared uncertainty. | current |
| JMR-H1-E02 | custody | JMR-H1-DP-01 | custody-recorded | The observation is transferred through a public-safety provenance ledger. | current |
| JMR-H1-E03 | transform | JMR-H1-DP-02 | derived-from-source | Location precision is minimized before joint distribution. | current |
| JMR-H1-E04 | version | JMR-H1-DP-02 | version-attested | The emergency-access schema and translation bundle are locked. | current |
| JMR-H1-E05 | evidence | JMR-H1-DP-03 | qualified-with-contrary-record | A ground report supports the blockage while a delayed report challenges severity. | current |
| JMR-H1-E06 | trust | JMR-H1-DP-03 | trust-decision-current | The source identity and transformation workload are authenticated. | current |
| JMR-H1-E07 | release | JMR-H1-DP-04 | release-current-for-declared-purpose | The minimized product is permitted for emergency-routing support. | current |
| JMR-H1-E08 | reachability | JMR-H1-THREAD-01 | technical-state-current | Two abstract paths are compared for timing, capacity, and shared gateway risk. | current |
| JMR-H1-E09 | authority | JMR-H1-THREAD-01 | authority-record-current | A fictional coordination authority is current for emergency support only. | current |
| JMR-H1-E10 | recommendation | JMR-H1-THREAD-01 | rationale-linked-to-evidence | The composer recommends continued collection and an alternate supply route. | current |
| JMR-H1-E11 | human-review | JMR-H1-THREAD-01 | review-record-complete | A qualified reviewer inspects evidence, uncertainty, and alternatives before confirming the bounded recommendation. | current |
| JMR-H1-E12 | assessment | JMR-H1-ASSESS-01 | assessment-current-with-residual-unknowns | Later field assessment records partial restoration and unresolved access uncertainty. | current |
| Alternative | Original status | Current status | Reason |
|---|---|---|---|
| Original selected bounded thread | selected | selected | Satisfied the fictional declared evidence, trust, release, capacity, authority, and review conditions. |
| Held alternate thread | held | held | Retained as an alternative but held for one declared semantic, capacity, or trust qualification. |
| Rejected out-of-purpose thread | rejected | rejected | Technically reachable but outside the fictional permitted purpose or authority scope. |
Human-review conditions
- Evidence Access
- Yes
- Contrary Evidence Visible
- Yes
- Time Sufficient
- Yes
- Competence Declared
- Yes
- Authority Current
- Yes
- Intervention Power
- Yes
- Review Type
- merits
Invalidated, suspended, or changed records
- No event changed under the selected later-change state.
Records still unchanged
- JMR-H1-E01: Source observation created
- JMR-H1-E02: Custody and provenance registered
- JMR-H1-E03: Data minimized and transformed
- JMR-H1-E04: Semantic and software versions locked
- JMR-H1-E05: Evidence and contrary evidence qualified
- JMR-H1-E06: Identity and workload trust evaluated
- JMR-H1-E07: Release and permitted purpose decided
- JMR-H1-E08: Reachability, timing, capacity, and failure domains checked
- JMR-H1-E09: Delegated authority and expiry checked
- JMR-H1-E10: Bounded machine coordination output produced
- JMR-H1-E11: Human merits review recorded
- JMR-H1-E12: Assessment and residual unknowns recorded
No composite replay, provenance, JADC2, interoperability, trust, authority, readiness, confidence, legality, safety, accountability, or certification score. No composite replay, provenance, JADC2, interoperability, trust, authority, readiness, confidence, legality, safety, accountability, operational-acceptance, or certification score is calculated.
Mission-thread replay ready. Replay creates no force, legal, certification, or deployment authority.
Interpretation rules
The current view may be less supportable than the original history.
Later evidence and change do not erase history. They change what can be relied upon now.
Preserve original and current state
Never overwrite a historical record with the current state. Store the correction, revocation, expiry, contradiction, and dependency effects separately.
Propagate invalidation
A corrected source or revoked data product must affect every declared downstream transformation, recommendation, review, action, and assessment.
Reconcile before resuming
Partition healing requires task, evidence, version, and authority reconciliation—not a last-writer-wins shortcut.
Fresh review does not create authority
An independent reviewer may require correction or withdrawal. Review completion alone does not authorize action, force, certification, or deployment.
Public and operational boundary
This is evidence education, not an operational command-and-control system.
The lab uses fixed fictional non-force histories and allowlisted changes. It cannot select or rank targets, assign weapons, recommend engagement, plan routes, allocate force, estimate casualties or mission success, authorize force, certify a system, approve deployment, ingest real evidence, or call Evulgare at runtime.
For separately governed real-system evidence, provenance, authority, assurance, and failure reconstruction, follow the ordinary user-initiated link to Evulgare. KillWebs.com transfers no data or state.
- Replay
- Reconstructs declared fictional history.
- Reconciliation
- Produces a coherent current technical and evidentiary state.
- Authority
- Remains separate and cannot be created by either replay or reconciliation.
Direct answers
JADC2 evidence and reconciliation replay FAQ
What is a JADC2 mission-thread replay?
It reconstructs a fixed fictional history linking source records, transformations, versions, trust, releasability, permitted use, authority, alternatives, human review, bounded coordination, assessment, and later invalidating changes.
Does a replay prove that the original mission-thread decision was correct?
No. A replay can show the declared history and dependencies. It does not validate evidence accuracy, decision quality, legality, safety, authority, operational effectiveness, certification, or deployment readiness.
Why does a corrected source affect downstream records?
A derived transformation, interpretation, recommendation, review, action, or assessment may depend on that source. The correction must therefore propagate through the dependency graph while the original history remains visible.
Does restoring a connection restore authority?
No. A healed network partition may still contain conflicting state, task ownership, versions, release decisions, or expired authority. Reconciliation and current review remain separate requirements.
When is a recorded human action only procedural?
When the record cannot establish what evidence and alternatives were shown, how much time was available, whether the reviewer was competent and authorized, or whether intervention could still change the outcome.
Can this lab ingest real logs or transfer evidence to Evulgare?
No. It accepts only one allowlisted fictional history and one allowlisted change. It accepts no files, real logs, evidence, URLs, organizations, people, targets, systems, credentials, operational data, or runtime Evulgare handoff.
Ecosystem handoff
When the question becomes real mission-thread evidence, decision provenance, authority history, and reconciliation, continue at Evulgare.
KillWebs.com explains the concept with public research and fixed fictional records. Evulgare is the separate evidence layer for real consequential systems: what the machine knew, what it did not know, which software and models were operating, what authority existed, what information the human received, and where failure originated.
Stop using software that blames the human. Let Evulgare’s machine intelligence answer for the machine by preserving and producing the technical account, so a person is not forced to defend behavior they could not see, verify, understand, challenge, or control. This is technical answerability—not automated legal liability.
RESPONSIBILITY SHOULD FOLLOW THE EVIDENCE.
A HUMAN CLICK IS NOT A LIABILITY TRANSFER.