Tools

KillWebs.comComposable mission networks

What the evidence can see—and what it cannot

JADC2 Assurance Evidence Coverage and Blind-Spot Lab

Inspect six fixed fictional Joint All-Domain Command and Control assurance cases and see whether collection, provenance, exact versions, identity, trusted time, authority, human review, monitoring, assessment, correction, reconciliation, and independent review are actually covered.

Research basis KW-RPT-002 KW-RPT-007 KW-RPT-011 KW-RPT-013 KW-RPT-038 KW-RPT-041 KW-RPT-042 KW-RPT-043 KW-RPT-046 KW-RPT-047

Coverage is an evidence claim

No alert is not proof that no failure occurred.

JADC2 means Joint All-Domain Command and Control. CJADC2 means Combined Joint All-Domain Command and Control. The lab asks which consequential conditions were observed, which were not, which records were never created, and whether the monitor is independent from the failure it is expected to detect.

A monitoring dashboard can look complete while missing the interval, dependency, version, authority state, interface condition, or downstream correction that matters most. The absence of a record therefore remains separate from evidence that a condition did not occur.

Governing definitions

Keep coverage, missing evidence, evidence never created, blind spots, and monitor independence separate.

jadc2Joint All-Domain Command and Control

cjadc2Combined Joint All-Domain Command and Control

coverageDeclared evidence that a consequential condition, interval, dependency, or review state was observed within stated bounds.

blind spotA condition, interval, dependency, or failure mode that the evidence system cannot reliably observe.

missing evidenceExpected evidence that should exist but is unavailable.

never created evidenceEvidence the architecture never generated, making retroactive reconstruction impossible without independent sources.

monitor independenceEvidence that the monitor does not share the relevant defect, lineage, administrator, infrastructure, data, identity, or control plane it is intended to detect.

Sixteen independent evidence-coverage dimensions

Coverage must span the complete evidence, authority, human-review, assessment, correction, and recovery chain.

JAC-DIM-01

Source collection and observation coverage

Whether expected sources were active, sampled, retained, and capable of observing the represented condition.

Coverage requirement: Document source schedule, expected observations, retention, blind periods, and sampling limits.

Blind spot: A source list does not prove continuous observation or coverage of consequential intervals.

Independence: At least one review or monitor must not share the relevant code, data, identity, administrator, infrastructure, or control plane it evaluates.

JAC-DIM-02

Source identity, custody, and provenance

Whether source identity, custody, collection context, provenance, and chain of derivation remain complete.

Coverage requirement: Preserve identity, custody, hashes, provenance links, and correction history.

Blind spot: A present file can still have incomplete custody or provenance.

Independence: At least one review or monitor must not share the relevant code, data, identity, administrator, infrastructure, or control plane it evaluates.

JAC-DIM-03

Transformations, minimization, and derived products

Whether transformations, redactions, aggregation, minimization, and derived-product dependencies are visible.

Coverage requirement: Record every transformation, information loss, minimization rule, and downstream dependency.

Blind spot: A derived record can hide information loss or unsupported inference.

Independence: At least one review or monitor must not share the relevant code, data, identity, administrator, infrastructure, or control plane it evaluates.

JAC-DIM-04

Exact software, model, configuration, and policy versions

Whether the exact deployed software, model, configuration, policy, builder, and artifact identities were captured.

Coverage requirement: Capture hashes, builder identity, configuration, policy, and runtime attestation.

Blind spot: A product or release label does not prove which artifact actually executed.

Independence: At least one review or monitor must not share the relevant code, data, identity, administrator, infrastructure, or control plane it evaluates.

JAC-DIM-05

Semantic schema, translator, and compatibility state

Whether schemas, ontologies, units, translator versions, and semantic assumptions were observed and compatible.

Coverage requirement: Preserve schema versions, translator identity, units, ontology mappings, and compatibility tests.

Blind spot: Readable data can still be semantically wrong or translated under a different rule set.

Independence: At least one review or monitor must not share the relevant code, data, identity, administrator, infrastructure, or control plane it evaluates.

JAC-DIM-06

Identity, workload trust, and authorization services

Whether identities, trust roots, workload state, authorization services, revocation, and policy enforcement were observed.

Coverage requirement: Observe trust roots, identities, revocation, workload health, and policy-decision state.

Blind spot: An authenticated sender does not prove trustworthy evidence or current authority.

Independence: At least one review or monitor must not share the relevant code, data, identity, administrator, infrastructure, or control plane it evaluates.

JAC-DIM-07

Trusted time, synchronization, freshness, and latency

Whether trusted time, synchronization, evidence age, latency, and freshness were measured for the consequential interval.

Coverage requirement: Preserve time-source identity, offset, holdover, freshness, and timing blind periods.

Blind spot: A timestamp without trusted-time health does not prove when a state was valid.

Independence: At least one review or monitor must not share the relevant code, data, identity, administrator, infrastructure, or control plane it evaluates.

JAC-DIM-08

Data quality, calibration, uncertainty, and contrary evidence

Whether calibration, uncertainty, known limits, contrary evidence, and independent observations were available.

Coverage requirement: Expose calibration, uncertainty decomposition, contrary channels, dependence, and known limitations.

Blind spot: High confidence and many observations do not establish truth or independence.

Independence: At least one review or monitor must not share the relevant code, data, identity, administrator, infrastructure, or control plane it evaluates.

JAC-DIM-09

Releasability, permitted purpose, and downstream use

Whether sensitivity, releasability, permitted purpose, prohibited purpose, minimization, and downstream use were observed.

Coverage requirement: Preserve purpose, releasability, recipient, minimization, expiry, and revocation evidence.

Blind spot: Available or previously released data may not be permitted for the current purpose.

Independence: At least one review or monitor must not share the relevant code, data, identity, administrator, infrastructure, or control plane it evaluates.

JAC-DIM-10

Authority, delegation, expiry, and revocation

Whether delegation, authority scope, expiry, revocation, exception state, and return-of-control conditions were recorded.

Coverage requirement: Capture authority source, scope, validity, revocation, exception, and handback state.

Blind spot: Connection restoration or technical capability does not restore authority.

Independence: At least one review or monitor must not share the relevant code, data, identity, administrator, infrastructure, or control plane it evaluates.

JAC-DIM-11

Human interface, evidence presentation, time, and intervention

Whether the record shows what the human received, what was hidden, available time, competence, authority, and practical intervention power.

Coverage requirement: Preserve interface state, evidence access, alternatives, timing, workload, action, and intervention capability.

Blind spot: A recorded click does not establish meaningful human judgment.

Independence: At least one review or monitor must not share the relevant code, data, identity, administrator, infrastructure, or control plane it evaluates.

JAC-DIM-12

Continuous monitoring, health, alerts, and blind periods

Whether monitor health, alert paths, retention, blind periods, and monitoring limitations were independently observed.

Coverage requirement: Observe monitor health, alert delivery, retention, independence, blind periods, and common-mode dependencies.

Blind spot: A monitor can share the defect, administrator, data, or control plane it is meant to detect.

Independence: At least one review or monitor must not share the relevant code, data, identity, administrator, infrastructure, or control plane it evaluates.

JAC-DIM-13

Outcome assessment, consequences, and remedy evidence

Whether outcomes, contradictory assessment, downstream consequences, technical correction, and remedy evidence were created.

Coverage requirement: Preserve assessment, consequences, contradictory findings, correction, and remedy status.

Blind spot: No outcome record does not establish that no consequence occurred.

Independence: At least one review or monitor must not share the relevant code, data, identity, administrator, infrastructure, or control plane it evaluates.

JAC-DIM-14

Correction propagation through dependent products and claims

Whether a corrected source invalidated or updated every dependent transformation, product, recommendation, claim, and cache.

Coverage requirement: Trace correction through all dependencies and retain the superseded history.

Blind spot: Correcting the source does not automatically correct downstream products.

Independence: At least one review or monitor must not share the relevant code, data, identity, administrator, infrastructure, or control plane it evaluates.

JAC-DIM-15

Partition, reconciliation, recovery, and return of control

Whether partition state, task ownership, divergent data, reconciliation, recovery, and return of control were observed.

Coverage requirement: Preserve partition history, divergent state, reconciliation evidence, recovery, and accountable handback.

Blind spot: A healed connection does not prove state reconciliation or restored authority.

Independence: At least one review or monitor must not share the relevant code, data, identity, administrator, infrastructure, or control plane it evaluates.

JAC-DIM-16

Independent review, monitor independence, and residual unknowns

Whether review and monitoring are independent from the code, data, administrator, infrastructure, and control plane under examination.

Coverage requirement: Document independence, competence, evidence access, scope, limitations, residual unknowns, and publication boundary.

Blind spot: Naming an independent monitor does not prove independent implementation or control.

Independence: At least one review or monitor must not share the relevant code, data, identity, administrator, infrastructure, or control plane it evaluates.

Six fixed fictional case families

The same monitoring gap can affect several apparently separate mission threads.

JAC-CASE-01

Disaster-response information routing

A fictional multi-organization network routes infrastructure-damage observations to a bounded coordination service.

Domain: Joint emergency support

Declared dimensions: 12

JAC-CASE-02

Infrastructure-protection coordination

A fictional protective network coordinates sensor, maintenance, and service-continuity information without modeling force.

Domain: Critical infrastructure protection

Declared dimensions: 12

JAC-CASE-03

Mission-partner awareness and releasability

A fictional mission partner contributes a minimized awareness product under explicit releasability and purpose conditions.

Domain: Combined information sharing

Declared dimensions: 12

JAC-CASE-04

Logistics recovery after gateway loss

A fictional logistics thread reroutes status data after a gateway fails and later reconnects with divergent state.

Domain: Contested logistics support

Declared dimensions: 10

JAC-CASE-05

Cyber-defense interpretation with contradictory evidence

A fictional defensive system compares anomaly evidence and a benign explanation before recommending containment.

Domain: Defensive cyber coordination

Declared dimensions: 11

JAC-CASE-06

Time-critical protective support

A fictional protective thread operates under a short authority window and explicit human-review conditions.

Domain: Protective decision support

Declared dimensions: 16

Eighteen abstract evidence, monitoring, review, and governance roles

Coverage claims require named responsibility without pretending a listed role completed the work.

JAC-ROLE-01

Collection coverage owner

Maintains declared source coverage, sampling intervals, blind periods, retention, and expected observations.

Role type: evidence role

JAC-ROLE-02

Custody and provenance steward

Maintains source identity, custody, provenance, chain of derivation, and evidence authenticity.

Role type: evidence role

JAC-ROLE-03

Transformation and minimization owner

Maintains transformations, redactions, minimization, derived products, and information-loss records.

Role type: data role

JAC-ROLE-04

Software and model state custodian

Maintains exact software, model, configuration, policy, builder, and deployed-artifact identity.

Role type: implementation role

JAC-ROLE-05

Semantic interoperability owner

Maintains schema, translator, units, ontology, compatibility, and semantic-version evidence.

Role type: data role

JAC-ROLE-06

Identity and trust service owner

Maintains identity, workload trust, authorization-service health, revocation, and trust-root evidence.

Role type: security role

JAC-ROLE-07

Trusted-time and synchronization owner

Maintains timing sources, synchronization state, clock health, freshness, and blind-period evidence.

Role type: infrastructure role

JAC-ROLE-08

Data-quality and uncertainty steward

Maintains calibration, uncertainty, representativeness, contrary evidence, and known data-quality limits.

Role type: evidence role

JAC-ROLE-09

Purpose and releasability owner

Maintains permitted purpose, prohibited use, releasability, minimization, and downstream-use limits.

Role type: governance role

JAC-ROLE-10

Delegation and authority owner

Maintains delegation, authority scope, expiry, revocation, and return-of-control conditions.

Role type: governance role

JAC-ROLE-11

Human-interface evidence owner

Maintains what the human saw, contrary evidence, alternatives, time, competence, authority, and intervention capability.

Role type: human-factors role

JAC-ROLE-12

Continuous monitoring owner

Maintains monitor health, alert-path coverage, blind periods, retention, and monitoring limitations.

Role type: monitoring role

JAC-ROLE-13

Outcome and consequence assessor

Maintains outcome assessment, consequences, remedy evidence, and contradictory post-event findings.

Role type: assessment role

JAC-ROLE-14

Correction-propagation owner

Tracks source corrections through transformations, data products, decisions, claims, caches, and dependent cases.

Role type: evidence role

JAC-ROLE-15

Reconciliation and recovery owner

Maintains partition history, divergent state, reconciliation, recovery, and return-of-control evidence.

Role type: recovery role

JAC-ROLE-16

Independent verification reviewer

Reviews coverage outside the originating code, data, administrator, monitoring, and control plane.

Role type: review role

JAC-ROLE-17

Portfolio assurance owner

Maintains direct and transitive claim and case impacts without converting coverage into certification.

Role type: assurance role

JAC-ROLE-18

Residual-unknowns and publication reviewer

Preserves unresolved uncertainty, public-safe wording, and the distinction between publication and operational authority.

Role type: review role

Sixteen required distinctions

Do not let monitoring theater become assurance.

No alert

is not the same as

No failure

Monitoring present

is not the same as

Monitoring complete

Coverage by count

is not the same as

Coverage of consequential conditions

Event log

is not the same as

Decision provenance

Observed component

is not the same as

Observed end-to-end behavior

One sampled condition

is not the same as

Operating-envelope coverage

Passing monitor

is not the same as

Independent verification

Known blind spot

is not the same as

Controlled blind spot

Corrected source

is not the same as

Corrected downstream products

Monitoring restored

is not the same as

Missing-period evidence recovered

Independent monitor name

is not the same as

Independent implementation or control plane

Recorded human action

is not the same as

Meaningful human judgment

Connection restored

is not the same as

Authority restored or state reconciled

Historical coverage

is not the same as

Current evidence support

Complete coverage graph

is not the same as

Safety, readiness, certification, or authority

Publication approval

is not the same as

Force authorization

Fixed synthetic workbench

Select one fictional case and one allowlisted coverage change.

Case family

Coverage change

The ordinary POST form is authoritative and works without JavaScript. No result is sent to Evulgare, KillChains.com, or another service.

Original postureEvidence coverage supportable within declared bounds

qualified

Current postureEvidence coverage supportable within declared bounds

qualified

Focus caseDisaster-response information routing

JAC-CASE-01

CertificationNo

No real-system determination is made.

The fixed fictional case has declared coverage for the represented conditions, with known limits and residual unknowns preserved.

No composite coverage, observability, trust, confidence, readiness, safety, authority, legal, compliance, certification, accreditation, or deployment score is calculated.

Cases affected0

Dimensions affected0

Evidence affected0

Activities affected0

Review roles0

Containment and holds

Maintain the standing bounded public-synthetic posture.

Required evidence generation

Continue declared evidence generation and monitoring.

Repeated-condition tests

Continue declared repeated-condition and monitor-health tests.

Correction propagation

No additional correction propagation is selected.

Reconciliation and return of control

Maintain standing reconciliation and accountable handback conditions.

Required reviewers

Standing evidence, monitoring, assurance, and independent-review roles.

Warnings

The baseline is supportable only for the fixed fictional scope; it is not proof of complete real-world observability.

Residual unknowns

Unmodeled conditions, hidden common dependencies, and evidence that was never expected by the public catalog may remain outside the graph.
The fixed public coverage graph cannot establish real-system safety, readiness, legality, command authority, force authorization, certification, accreditation, or deployment approval.

Blind periods

No additional blind period selected.

Missing expected evidence

No additional expected evidence is missing in the baseline.

Evidence never created

No additional never-created evidence selected.

Stale records

No additional stale record selected.

Contradictions

No additional contradiction selected.

Invalidations

No additional invalidation selected.

Unobserved conditions

No additional unobserved condition selected.

Monitor common mode

No additional monitor common-mode condition is selected in the fixed scenario; independence remains bounded by declared evidence.

No additional common dependency selected.

Dimension ledger

Dimension	Original	Current	Impact	Coverage requirement	Blind spot
`JAC-DIM-01` Source collection and observation coverage	covered-with-qualifications	covered-with-qualifications	none	Document source schedule, expected observations, retention, blind periods, and sampling limits.	A source list does not prove continuous observation or coverage of consequential intervals.
`JAC-DIM-02` Source identity, custody, and provenance	covered-with-qualifications	covered-with-qualifications	none	Preserve identity, custody, hashes, provenance links, and correction history.	A present file can still have incomplete custody or provenance.
`JAC-DIM-03` Transformations, minimization, and derived products	covered-with-qualifications	covered-with-qualifications	none	Record every transformation, information loss, minimization rule, and downstream dependency.	A derived record can hide information loss or unsupported inference.
`JAC-DIM-04` Exact software, model, configuration, and policy versions	covered-with-qualifications	covered-with-qualifications	none	Capture hashes, builder identity, configuration, policy, and runtime attestation.	A product or release label does not prove which artifact actually executed.
`JAC-DIM-05` Semantic schema, translator, and compatibility state	covered-with-qualifications	covered-with-qualifications	none	Preserve schema versions, translator identity, units, ontology mappings, and compatibility tests.	Readable data can still be semantically wrong or translated under a different rule set.
`JAC-DIM-06` Identity, workload trust, and authorization services	covered-with-qualifications	covered-with-qualifications	none	Observe trust roots, identities, revocation, workload health, and policy-decision state.	An authenticated sender does not prove trustworthy evidence or current authority.
`JAC-DIM-07` Trusted time, synchronization, freshness, and latency	covered-with-qualifications	covered-with-qualifications	none	Preserve time-source identity, offset, holdover, freshness, and timing blind periods.	A timestamp without trusted-time health does not prove when a state was valid.
`JAC-DIM-08` Data quality, calibration, uncertainty, and contrary evidence	covered-with-qualifications	covered-with-qualifications	none	Expose calibration, uncertainty decomposition, contrary channels, dependence, and known limitations.	High confidence and many observations do not establish truth or independence.
`JAC-DIM-09` Releasability, permitted purpose, and downstream use	covered-with-qualifications	covered-with-qualifications	none	Preserve purpose, releasability, recipient, minimization, expiry, and revocation evidence.	Available or previously released data may not be permitted for the current purpose.
`JAC-DIM-10` Authority, delegation, expiry, and revocation	covered-with-qualifications	covered-with-qualifications	none	Capture authority source, scope, validity, revocation, exception, and handback state.	Connection restoration or technical capability does not restore authority.
`JAC-DIM-11` Human interface, evidence presentation, time, and intervention	covered-with-qualifications	covered-with-qualifications	none	Preserve interface state, evidence access, alternatives, timing, workload, action, and intervention capability.	A recorded click does not establish meaningful human judgment.
`JAC-DIM-12` Continuous monitoring, health, alerts, and blind periods	covered-with-qualifications	covered-with-qualifications	none	Observe monitor health, alert delivery, retention, independence, blind periods, and common-mode dependencies.	A monitor can share the defect, administrator, data, or control plane it is meant to detect.
`JAC-DIM-13` Outcome assessment, consequences, and remedy evidence	covered-with-qualifications	covered-with-qualifications	none	Preserve assessment, consequences, contradictory findings, correction, and remedy status.	No outcome record does not establish that no consequence occurred.
`JAC-DIM-14` Correction propagation through dependent products and claims	covered-with-qualifications	covered-with-qualifications	none	Trace correction through all dependencies and retain the superseded history.	Correcting the source does not automatically correct downstream products.
`JAC-DIM-15` Partition, reconciliation, recovery, and return of control	covered-with-qualifications	covered-with-qualifications	none	Preserve partition history, divergent state, reconciliation evidence, recovery, and accountable handback.	A healed connection does not prove state reconciliation or restored authority.
`JAC-DIM-16` Independent review, monitor independence, and residual unknowns	covered-with-qualifications	covered-with-qualifications	none	Document independence, competence, evidence access, scope, limitations, residual unknowns, and publication boundary.	Naming an independent monitor does not prove independent implementation or control.

Evidence and monitoring ledger

Evidence	Dimension	Original	Current	Impact	Limitations
`JAC-EVD-01` Source collection and observation coverage evidence record	`JAC-DIM-01`	present-and-qualified	present-and-qualified	none	A source list does not prove continuous observation or coverage of consequential intervals.
`JAC-EVD-02` Source identity, custody, and provenance evidence record	`JAC-DIM-02`	present-and-qualified	present-and-qualified	none	A present file can still have incomplete custody or provenance.
`JAC-EVD-03` Transformations, minimization, and derived products evidence record	`JAC-DIM-03`	present-and-qualified	present-and-qualified	none	A derived record can hide information loss or unsupported inference.
`JAC-EVD-04` Exact software, model, configuration, and policy versions evidence record	`JAC-DIM-04`	present-and-qualified	present-and-qualified	none	A product or release label does not prove which artifact actually executed.
`JAC-EVD-05` Semantic schema, translator, and compatibility state evidence record	`JAC-DIM-05`	present-and-qualified	present-and-qualified	none	Readable data can still be semantically wrong or translated under a different rule set.
`JAC-EVD-06` Identity, workload trust, and authorization services evidence record	`JAC-DIM-06`	present-and-qualified	present-and-qualified	none	An authenticated sender does not prove trustworthy evidence or current authority.
`JAC-EVD-07` Trusted time, synchronization, freshness, and latency evidence record	`JAC-DIM-07`	present-and-qualified	present-and-qualified	none	A timestamp without trusted-time health does not prove when a state was valid.
`JAC-EVD-08` Data quality, calibration, uncertainty, and contrary evidence evidence record	`JAC-DIM-08`	present-and-qualified	present-and-qualified	none	High confidence and many observations do not establish truth or independence.
`JAC-EVD-09` Releasability, permitted purpose, and downstream use evidence record	`JAC-DIM-09`	present-and-qualified	present-and-qualified	none	Available or previously released data may not be permitted for the current purpose.
`JAC-EVD-10` Authority, delegation, expiry, and revocation evidence record	`JAC-DIM-10`	present-and-qualified	present-and-qualified	none	Connection restoration or technical capability does not restore authority.
`JAC-EVD-11` Human interface, evidence presentation, time, and intervention evidence record	`JAC-DIM-11`	present-and-qualified	present-and-qualified	none	A recorded click does not establish meaningful human judgment.
`JAC-EVD-12` Continuous monitoring, health, alerts, and blind periods evidence record	`JAC-DIM-12`	present-and-qualified	present-and-qualified	none	A monitor can share the defect, administrator, data, or control plane it is meant to detect.
`JAC-EVD-13` Outcome assessment, consequences, and remedy evidence evidence record	`JAC-DIM-13`	present-and-qualified	present-and-qualified	none	No outcome record does not establish that no consequence occurred.
`JAC-EVD-14` Correction propagation through dependent products and claims evidence record	`JAC-DIM-14`	present-and-qualified	present-and-qualified	none	Correcting the source does not automatically correct downstream products.
`JAC-EVD-15` Partition, reconciliation, recovery, and return of control evidence record	`JAC-DIM-15`	present-and-qualified	present-and-qualified	none	A healed connection does not prove state reconciliation or restored authority.
`JAC-EVD-16` Independent review, monitor independence, and residual unknowns evidence record	`JAC-DIM-16`	present-and-qualified	present-and-qualified	none	Naming an independent monitor does not prove independent implementation or control.

Verification and monitoring activities

Activity	Dimension	Original	Current	Method	Independence
`JAC-ACT-01` Source collection and observation coverage verification or monitoring activity	`JAC-DIM-01`	complete-with-qualifications	complete-with-qualifications	Fixed synthetic inspection, repeated-condition testing, and dependency review.	The activity must disclose shared implementation, data, administrator, identity, infrastructure, and verification dependencies.
`JAC-ACT-02` Source identity, custody, and provenance verification or monitoring activity	`JAC-DIM-02`	complete-with-qualifications	complete-with-qualifications	Fixed synthetic inspection, repeated-condition testing, and dependency review.	The activity must disclose shared implementation, data, administrator, identity, infrastructure, and verification dependencies.
`JAC-ACT-03` Transformations, minimization, and derived products verification or monitoring activity	`JAC-DIM-03`	complete-with-qualifications	complete-with-qualifications	Fixed synthetic inspection, repeated-condition testing, and dependency review.	The activity must disclose shared implementation, data, administrator, identity, infrastructure, and verification dependencies.
`JAC-ACT-04` Exact software, model, configuration, and policy versions verification or monitoring activity	`JAC-DIM-04`	complete-with-qualifications	complete-with-qualifications	Fixed synthetic inspection, repeated-condition testing, and dependency review.	The activity must disclose shared implementation, data, administrator, identity, infrastructure, and verification dependencies.
`JAC-ACT-05` Semantic schema, translator, and compatibility state verification or monitoring activity	`JAC-DIM-05`	complete-with-qualifications	complete-with-qualifications	Fixed synthetic inspection, repeated-condition testing, and dependency review.	The activity must disclose shared implementation, data, administrator, identity, infrastructure, and verification dependencies.
`JAC-ACT-06` Identity, workload trust, and authorization services verification or monitoring activity	`JAC-DIM-06`	complete-with-qualifications	complete-with-qualifications	Fixed synthetic inspection, repeated-condition testing, and dependency review.	The activity must disclose shared implementation, data, administrator, identity, infrastructure, and verification dependencies.
`JAC-ACT-07` Trusted time, synchronization, freshness, and latency verification or monitoring activity	`JAC-DIM-07`	complete-with-qualifications	complete-with-qualifications	Fixed synthetic inspection, repeated-condition testing, and dependency review.	The activity must disclose shared implementation, data, administrator, identity, infrastructure, and verification dependencies.
`JAC-ACT-08` Data quality, calibration, uncertainty, and contrary evidence verification or monitoring activity	`JAC-DIM-08`	complete-with-qualifications	complete-with-qualifications	Fixed synthetic inspection, repeated-condition testing, and dependency review.	The activity must disclose shared implementation, data, administrator, identity, infrastructure, and verification dependencies.
`JAC-ACT-09` Releasability, permitted purpose, and downstream use verification or monitoring activity	`JAC-DIM-09`	complete-with-qualifications	complete-with-qualifications	Fixed synthetic inspection, repeated-condition testing, and dependency review.	The activity must disclose shared implementation, data, administrator, identity, infrastructure, and verification dependencies.
`JAC-ACT-10` Authority, delegation, expiry, and revocation verification or monitoring activity	`JAC-DIM-10`	complete-with-qualifications	complete-with-qualifications	Fixed synthetic inspection, repeated-condition testing, and dependency review.	The activity must disclose shared implementation, data, administrator, identity, infrastructure, and verification dependencies.
`JAC-ACT-11` Human interface, evidence presentation, time, and intervention verification or monitoring activity	`JAC-DIM-11`	complete-with-qualifications	complete-with-qualifications	Fixed synthetic inspection, repeated-condition testing, and dependency review.	The activity must disclose shared implementation, data, administrator, identity, infrastructure, and verification dependencies.
`JAC-ACT-12` Continuous monitoring, health, alerts, and blind periods verification or monitoring activity	`JAC-DIM-12`	complete-with-qualifications	complete-with-qualifications	Fixed synthetic inspection, repeated-condition testing, and dependency review.	The activity must disclose shared implementation, data, administrator, identity, infrastructure, and verification dependencies.
`JAC-ACT-13` Outcome assessment, consequences, and remedy evidence verification or monitoring activity	`JAC-DIM-13`	complete-with-qualifications	complete-with-qualifications	Fixed synthetic inspection, repeated-condition testing, and dependency review.	The activity must disclose shared implementation, data, administrator, identity, infrastructure, and verification dependencies.
`JAC-ACT-14` Correction propagation through dependent products and claims verification or monitoring activity	`JAC-DIM-14`	complete-with-qualifications	complete-with-qualifications	Fixed synthetic inspection, repeated-condition testing, and dependency review.	The activity must disclose shared implementation, data, administrator, identity, infrastructure, and verification dependencies.
`JAC-ACT-15` Partition, reconciliation, recovery, and return of control verification or monitoring activity	`JAC-DIM-15`	complete-with-qualifications	complete-with-qualifications	Fixed synthetic inspection, repeated-condition testing, and dependency review.	The activity must disclose shared implementation, data, administrator, identity, infrastructure, and verification dependencies.
`JAC-ACT-16` Independent review, monitor independence, and residual unknowns verification or monitoring activity	`JAC-DIM-16`	complete-with-qualifications	complete-with-qualifications	Fixed synthetic inspection, repeated-condition testing, and dependency review.	The activity must disclose shared implementation, data, administrator, identity, infrastructure, and verification dependencies.

Case and claim impacts

Case	Focus	Affected	Current posture	Affected dimensions	Affected claims
`JAC-CASE-01` Disaster-response information routing	Yes	No	Evidence coverage supportable within declared bounds	None	None
`JAC-CASE-02` Infrastructure-protection coordination	No	No	Evidence coverage supportable within declared bounds	None	None
`JAC-CASE-03` Mission-partner awareness and releasability	No	No	Evidence coverage supportable within declared bounds	None	None
`JAC-CASE-04` Logistics recovery after gateway loss	No	No	Evidence coverage supportable within declared bounds	None	None
`JAC-CASE-05` Cyber-defense interpretation with contradictory evidence	No	No	Evidence coverage supportable within declared bounds	None	None
`JAC-CASE-06` Time-critical protective support	No	No	Evidence coverage supportable within declared bounds	None	None

Semantic relationship graph

The graph remains a semantic table so every relationship is available without Canvas or JavaScript.

Node	Type	Label	Current state	Depth
`JAC-CASE-01`	coverage-case	Disaster-response information routing	current	—
`JAR-CASE-01`	renewal-source-case	Imported renewal case JAR-CASE-01	current	—
`JAC-CASE-02`	coverage-case	Infrastructure-protection coordination	current	—
`JAR-CASE-02`	renewal-source-case	Imported renewal case JAR-CASE-02	current	—
`JAC-CASE-03`	coverage-case	Mission-partner awareness and releasability	current	—
`JAR-CASE-03`	renewal-source-case	Imported renewal case JAR-CASE-03	current	—
`JAC-CASE-04`	coverage-case	Logistics recovery after gateway loss	current	—
`JAR-CASE-04`	renewal-source-case	Imported renewal case JAR-CASE-04	current	—
`JAC-CASE-05`	coverage-case	Cyber-defense interpretation with contradictory evidence	current	—
`JAR-CASE-05`	renewal-source-case	Imported renewal case JAR-CASE-05	current	—
`JAC-CASE-06`	coverage-case	Time-critical protective support	current	—
`JAR-CASE-06`	renewal-source-case	Imported renewal case JAR-CASE-06	current	—
`JAC-DIM-01`	coverage-dimension	Source collection and observation coverage	current	—
`JAC-CLM-01`	coverage-claim	Coverage claim: Source collection and observation coverage	current	—
`JAC-DIM-02`	coverage-dimension	Source identity, custody, and provenance	current	—
`JAC-CLM-02`	coverage-claim	Coverage claim: Source identity, custody, and provenance	current	—
`JAC-DIM-03`	coverage-dimension	Transformations, minimization, and derived products	current	—
`JAC-CLM-03`	coverage-claim	Coverage claim: Transformations, minimization, and derived products	current	—
`JAC-DIM-04`	coverage-dimension	Exact software, model, configuration, and policy versions	current	—
`JAC-CLM-04`	coverage-claim	Coverage claim: Exact software, model, configuration, and policy versions	current	—
`JAC-DIM-05`	coverage-dimension	Semantic schema, translator, and compatibility state	current	—
`JAC-CLM-05`	coverage-claim	Coverage claim: Semantic schema, translator, and compatibility state	current	—
`JAC-DIM-06`	coverage-dimension	Identity, workload trust, and authorization services	current	—
`JAC-CLM-06`	coverage-claim	Coverage claim: Identity, workload trust, and authorization services	current	—
`JAC-DIM-07`	coverage-dimension	Trusted time, synchronization, freshness, and latency	current	—
`JAC-CLM-07`	coverage-claim	Coverage claim: Trusted time, synchronization, freshness, and latency	current	—
`JAC-DIM-08`	coverage-dimension	Data quality, calibration, uncertainty, and contrary evidence	current	—
`JAC-CLM-08`	coverage-claim	Coverage claim: Data quality, calibration, uncertainty, and contrary evidence	current	—
`JAC-DIM-09`	coverage-dimension	Releasability, permitted purpose, and downstream use	current	—
`JAC-CLM-09`	coverage-claim	Coverage claim: Releasability, permitted purpose, and downstream use	current	—
`JAC-DIM-10`	coverage-dimension	Authority, delegation, expiry, and revocation	current	—
`JAC-CLM-10`	coverage-claim	Coverage claim: Authority, delegation, expiry, and revocation	current	—
`JAC-DIM-11`	coverage-dimension	Human interface, evidence presentation, time, and intervention	current	—
`JAC-CLM-11`	coverage-claim	Coverage claim: Human interface, evidence presentation, time, and intervention	current	—
`JAC-DIM-12`	coverage-dimension	Continuous monitoring, health, alerts, and blind periods	current	—
`JAC-CLM-12`	coverage-claim	Coverage claim: Continuous monitoring, health, alerts, and blind periods	current	—
`JAC-DIM-13`	coverage-dimension	Outcome assessment, consequences, and remedy evidence	current	—
`JAC-CLM-13`	coverage-claim	Coverage claim: Outcome assessment, consequences, and remedy evidence	current	—
`JAC-DIM-14`	coverage-dimension	Correction propagation through dependent products and claims	current	—
`JAC-CLM-14`	coverage-claim	Coverage claim: Correction propagation through dependent products and claims	current	—
`JAC-DIM-15`	coverage-dimension	Partition, reconciliation, recovery, and return of control	current	—
`JAC-CLM-15`	coverage-claim	Coverage claim: Partition, reconciliation, recovery, and return of control	current	—
`JAC-DIM-16`	coverage-dimension	Independent review, monitor independence, and residual unknowns	current	—
`JAC-CLM-16`	coverage-claim	Coverage claim: Independent review, monitor independence, and residual unknowns	current	—
`JAC-ROLE-01`	role	Collection coverage owner	current	—
`JAC-ROLE-02`	role	Custody and provenance steward	current	—
`JAC-ROLE-03`	role	Transformation and minimization owner	current	—
`JAC-ROLE-04`	role	Software and model state custodian	current	—
`JAC-ROLE-05`	role	Semantic interoperability owner	current	—
`JAC-ROLE-06`	role	Identity and trust service owner	current	—
`JAC-ROLE-07`	role	Trusted-time and synchronization owner	current	—
`JAC-ROLE-08`	role	Data-quality and uncertainty steward	current	—
`JAC-ROLE-09`	role	Purpose and releasability owner	current	—
`JAC-ROLE-10`	role	Delegation and authority owner	current	—
`JAC-ROLE-11`	role	Human-interface evidence owner	current	—
`JAC-ROLE-12`	role	Continuous monitoring owner	current	—
`JAC-ROLE-13`	role	Outcome and consequence assessor	current	—
`JAC-ROLE-14`	role	Correction-propagation owner	current	—
`JAC-ROLE-15`	role	Reconciliation and recovery owner	current	—
`JAC-ROLE-16`	role	Independent verification reviewer	current	—
`JAC-ROLE-17`	role	Portfolio assurance owner	current	—
`JAC-ROLE-18`	role	Residual-unknowns and publication reviewer	current	—
`JAC-EVD-01`	evidence	Source collection and observation coverage evidence record	current	—
`JAC-EVD-02`	evidence	Source identity, custody, and provenance evidence record	current	—
`JAC-EVD-03`	evidence	Transformations, minimization, and derived products evidence record	current	—
`JAC-EVD-04`	evidence	Exact software, model, configuration, and policy versions evidence record	current	—
`JAC-EVD-05`	evidence	Semantic schema, translator, and compatibility state evidence record	current	—
`JAC-EVD-06`	evidence	Identity, workload trust, and authorization services evidence record	current	—
`JAC-EVD-07`	evidence	Trusted time, synchronization, freshness, and latency evidence record	current	—
`JAC-EVD-08`	evidence	Data quality, calibration, uncertainty, and contrary evidence evidence record	current	—
`JAC-EVD-09`	evidence	Releasability, permitted purpose, and downstream use evidence record	current	—
`JAC-EVD-10`	evidence	Authority, delegation, expiry, and revocation evidence record	current	—
`JAC-EVD-11`	evidence	Human interface, evidence presentation, time, and intervention evidence record	current	—
`JAC-EVD-12`	evidence	Continuous monitoring, health, alerts, and blind periods evidence record	current	—
`JAC-EVD-13`	evidence	Outcome assessment, consequences, and remedy evidence evidence record	current	—
`JAC-EVD-14`	evidence	Correction propagation through dependent products and claims evidence record	current	—
`JAC-EVD-15`	evidence	Partition, reconciliation, recovery, and return of control evidence record	current	—
`JAC-EVD-16`	evidence	Independent review, monitor independence, and residual unknowns evidence record	current	—
`JAC-ACT-01`	activity	Source collection and observation coverage verification or monitoring activity	current	—
`JAC-ACT-02`	activity	Source identity, custody, and provenance verification or monitoring activity	current	—
`JAC-ACT-03`	activity	Transformations, minimization, and derived products verification or monitoring activity	current	—
`JAC-ACT-04`	activity	Exact software, model, configuration, and policy versions verification or monitoring activity	current	—
`JAC-ACT-05`	activity	Semantic schema, translator, and compatibility state verification or monitoring activity	current	—
`JAC-ACT-06`	activity	Identity, workload trust, and authorization services verification or monitoring activity	current	—
`JAC-ACT-07`	activity	Trusted time, synchronization, freshness, and latency verification or monitoring activity	current	—
`JAC-ACT-08`	activity	Data quality, calibration, uncertainty, and contrary evidence verification or monitoring activity	current	—
`JAC-ACT-09`	activity	Releasability, permitted purpose, and downstream use verification or monitoring activity	current	—
`JAC-ACT-10`	activity	Authority, delegation, expiry, and revocation verification or monitoring activity	current	—
`JAC-ACT-11`	activity	Human interface, evidence presentation, time, and intervention verification or monitoring activity	current	—
`JAC-ACT-12`	activity	Continuous monitoring, health, alerts, and blind periods verification or monitoring activity	current	—
`JAC-ACT-13`	activity	Outcome assessment, consequences, and remedy evidence verification or monitoring activity	current	—
`JAC-ACT-14`	activity	Correction propagation through dependent products and claims verification or monitoring activity	current	—
`JAC-ACT-15`	activity	Partition, reconciliation, recovery, and return of control verification or monitoring activity	current	—
`JAC-ACT-16`	activity	Independent review, monitor independence, and residual unknowns verification or monitoring activity	current	—

Dependent	Relationship	Dependency	Current state
`JAC-CASE-01`	imports-stable-case	`JAR-CASE-01`	current
`JAC-CASE-01`	requires-coverage-claim	`JAC-CLM-01`	current
`JAC-CASE-01`	requires-coverage-claim	`JAC-CLM-02`	current
`JAC-CASE-01`	requires-coverage-claim	`JAC-CLM-03`	current
`JAC-CASE-01`	requires-coverage-claim	`JAC-CLM-04`	current
`JAC-CASE-01`	requires-coverage-claim	`JAC-CLM-05`	current
`JAC-CASE-01`	requires-coverage-claim	`JAC-CLM-07`	current
`JAC-CASE-01`	requires-coverage-claim	`JAC-CLM-08`	current
`JAC-CASE-01`	requires-coverage-claim	`JAC-CLM-10`	current
`JAC-CASE-01`	requires-coverage-claim	`JAC-CLM-11`	current
`JAC-CASE-01`	requires-coverage-claim	`JAC-CLM-12`	current
`JAC-CASE-01`	requires-coverage-claim	`JAC-CLM-13`	current
`JAC-CASE-01`	requires-coverage-claim	`JAC-CLM-16`	current
`JAC-CASE-02`	imports-stable-case	`JAR-CASE-02`	current
`JAC-CASE-02`	requires-coverage-claim	`JAC-CLM-01`	current
`JAC-CASE-02`	requires-coverage-claim	`JAC-CLM-02`	current
`JAC-CASE-02`	requires-coverage-claim	`JAC-CLM-03`	current
`JAC-CASE-02`	requires-coverage-claim	`JAC-CLM-04`	current
`JAC-CASE-02`	requires-coverage-claim	`JAC-CLM-05`	current
`JAC-CASE-02`	requires-coverage-claim	`JAC-CLM-06`	current
`JAC-CASE-02`	requires-coverage-claim	`JAC-CLM-07`	current
`JAC-CASE-02`	requires-coverage-claim	`JAC-CLM-08`	current
`JAC-CASE-02`	requires-coverage-claim	`JAC-CLM-09`	current
`JAC-CASE-02`	requires-coverage-claim	`JAC-CLM-12`	current
`JAC-CASE-02`	requires-coverage-claim	`JAC-CLM-14`	current
`JAC-CASE-02`	requires-coverage-claim	`JAC-CLM-16`	current
`JAC-CASE-03`	imports-stable-case	`JAR-CASE-03`	current
`JAC-CASE-03`	requires-coverage-claim	`JAC-CLM-01`	current
`JAC-CASE-03`	requires-coverage-claim	`JAC-CLM-02`	current
`JAC-CASE-03`	requires-coverage-claim	`JAC-CLM-05`	current
`JAC-CASE-03`	requires-coverage-claim	`JAC-CLM-06`	current
`JAC-CASE-03`	requires-coverage-claim	`JAC-CLM-07`	current
`JAC-CASE-03`	requires-coverage-claim	`JAC-CLM-08`	current
`JAC-CASE-03`	requires-coverage-claim	`JAC-CLM-09`	current
`JAC-CASE-03`	requires-coverage-claim	`JAC-CLM-10`	current
`JAC-CASE-03`	requires-coverage-claim	`JAC-CLM-11`	current
`JAC-CASE-03`	requires-coverage-claim	`JAC-CLM-12`	current
`JAC-CASE-03`	requires-coverage-claim	`JAC-CLM-14`	current
`JAC-CASE-03`	requires-coverage-claim	`JAC-CLM-16`	current
`JAC-CASE-04`	imports-stable-case	`JAR-CASE-04`	current
`JAC-CASE-04`	requires-coverage-claim	`JAC-CLM-01`	current
`JAC-CASE-04`	requires-coverage-claim	`JAC-CLM-04`	current
`JAC-CASE-04`	requires-coverage-claim	`JAC-CLM-06`	current
`JAC-CASE-04`	requires-coverage-claim	`JAC-CLM-07`	current
`JAC-CASE-04`	requires-coverage-claim	`JAC-CLM-10`	current
`JAC-CASE-04`	requires-coverage-claim	`JAC-CLM-12`	current
`JAC-CASE-04`	requires-coverage-claim	`JAC-CLM-13`	current
`JAC-CASE-04`	requires-coverage-claim	`JAC-CLM-14`	current
`JAC-CASE-04`	requires-coverage-claim	`JAC-CLM-15`	current
`JAC-CASE-04`	requires-coverage-claim	`JAC-CLM-16`	current
`JAC-CASE-05`	imports-stable-case	`JAR-CASE-05`	current
`JAC-CASE-05`	requires-coverage-claim	`JAC-CLM-01`	current
`JAC-CASE-05`	requires-coverage-claim	`JAC-CLM-02`	current
`JAC-CASE-05`	requires-coverage-claim	`JAC-CLM-03`	current
`JAC-CASE-05`	requires-coverage-claim	`JAC-CLM-04`	current
`JAC-CASE-05`	requires-coverage-claim	`JAC-CLM-06`	current
`JAC-CASE-05`	requires-coverage-claim	`JAC-CLM-07`	current
`JAC-CASE-05`	requires-coverage-claim	`JAC-CLM-08`	current
`JAC-CASE-05`	requires-coverage-claim	`JAC-CLM-12`	current
`JAC-CASE-05`	requires-coverage-claim	`JAC-CLM-13`	current
`JAC-CASE-05`	requires-coverage-claim	`JAC-CLM-15`	current
`JAC-CASE-05`	requires-coverage-claim	`JAC-CLM-16`	current
`JAC-CASE-06`	imports-stable-case	`JAR-CASE-06`	current
`JAC-CASE-06`	requires-coverage-claim	`JAC-CLM-01`	current
`JAC-CASE-06`	requires-coverage-claim	`JAC-CLM-02`	current
`JAC-CASE-06`	requires-coverage-claim	`JAC-CLM-03`	current
`JAC-CASE-06`	requires-coverage-claim	`JAC-CLM-04`	current
`JAC-CASE-06`	requires-coverage-claim	`JAC-CLM-05`	current
`JAC-CASE-06`	requires-coverage-claim	`JAC-CLM-06`	current
`JAC-CASE-06`	requires-coverage-claim	`JAC-CLM-07`	current
`JAC-CASE-06`	requires-coverage-claim	`JAC-CLM-08`	current
`JAC-CASE-06`	requires-coverage-claim	`JAC-CLM-09`	current
`JAC-CASE-06`	requires-coverage-claim	`JAC-CLM-10`	current
`JAC-CASE-06`	requires-coverage-claim	`JAC-CLM-11`	current
`JAC-CASE-06`	requires-coverage-claim	`JAC-CLM-12`	current
`JAC-CASE-06`	requires-coverage-claim	`JAC-CLM-13`	current
`JAC-CASE-06`	requires-coverage-claim	`JAC-CLM-14`	current
`JAC-CASE-06`	requires-coverage-claim	`JAC-CLM-15`	current
`JAC-CASE-06`	requires-coverage-claim	`JAC-CLM-16`	current
`JAC-CLM-01`	evaluates	`JAC-DIM-01`	current
`JAC-CLM-01`	supported-by	`JAC-EVD-01`	current
`JAC-CLM-01`	verified-by	`JAC-ACT-01`	current
`JAC-CLM-01`	reviewed-by	`JAC-ROLE-01`	current
`JAC-CLM-01`	reviewed-by	`JAC-ROLE-12`	current
`JAC-CLM-01`	reviewed-by	`JAC-ROLE-16`	current
`JAC-CLM-02`	evaluates	`JAC-DIM-02`	current
`JAC-CLM-02`	supported-by	`JAC-EVD-02`	current
`JAC-CLM-02`	verified-by	`JAC-ACT-02`	current
`JAC-CLM-02`	reviewed-by	`JAC-ROLE-02`	current
`JAC-CLM-02`	reviewed-by	`JAC-ROLE-14`	current
`JAC-CLM-02`	reviewed-by	`JAC-ROLE-16`	current
`JAC-CLM-03`	evaluates	`JAC-DIM-03`	current
`JAC-CLM-03`	supported-by	`JAC-EVD-03`	current
`JAC-CLM-03`	verified-by	`JAC-ACT-03`	current
`JAC-CLM-03`	reviewed-by	`JAC-ROLE-03`	current
`JAC-CLM-03`	reviewed-by	`JAC-ROLE-14`	current
`JAC-CLM-03`	reviewed-by	`JAC-ROLE-16`	current
`JAC-CLM-04`	evaluates	`JAC-DIM-04`	current
`JAC-CLM-04`	supported-by	`JAC-EVD-04`	current
`JAC-CLM-04`	verified-by	`JAC-ACT-04`	current
`JAC-CLM-04`	reviewed-by	`JAC-ROLE-04`	current
`JAC-CLM-04`	reviewed-by	`JAC-ROLE-16`	current
`JAC-CLM-04`	reviewed-by	`JAC-ROLE-17`	current
`JAC-CLM-05`	evaluates	`JAC-DIM-05`	current
`JAC-CLM-05`	supported-by	`JAC-EVD-05`	current
`JAC-CLM-05`	verified-by	`JAC-ACT-05`	current
`JAC-CLM-05`	reviewed-by	`JAC-ROLE-05`	current
`JAC-CLM-05`	reviewed-by	`JAC-ROLE-03`	current
`JAC-CLM-05`	reviewed-by	`JAC-ROLE-16`	current
`JAC-CLM-06`	evaluates	`JAC-DIM-06`	current
`JAC-CLM-06`	supported-by	`JAC-EVD-06`	current
`JAC-CLM-06`	verified-by	`JAC-ACT-06`	current
`JAC-CLM-06`	reviewed-by	`JAC-ROLE-06`	current
`JAC-CLM-06`	reviewed-by	`JAC-ROLE-10`	current
`JAC-CLM-06`	reviewed-by	`JAC-ROLE-16`	current
`JAC-CLM-07`	evaluates	`JAC-DIM-07`	current
`JAC-CLM-07`	supported-by	`JAC-EVD-07`	current
`JAC-CLM-07`	verified-by	`JAC-ACT-07`	current
`JAC-CLM-07`	reviewed-by	`JAC-ROLE-07`	current
`JAC-CLM-07`	reviewed-by	`JAC-ROLE-12`	current
`JAC-CLM-07`	reviewed-by	`JAC-ROLE-16`	current
`JAC-CLM-08`	evaluates	`JAC-DIM-08`	current
`JAC-CLM-08`	supported-by	`JAC-EVD-08`	current
`JAC-CLM-08`	verified-by	`JAC-ACT-08`	current
`JAC-CLM-08`	reviewed-by	`JAC-ROLE-08`	current
`JAC-CLM-08`	reviewed-by	`JAC-ROLE-13`	current
`JAC-CLM-08`	reviewed-by	`JAC-ROLE-16`	current
`JAC-CLM-09`	evaluates	`JAC-DIM-09`	current
`JAC-CLM-09`	supported-by	`JAC-EVD-09`	current
`JAC-CLM-09`	verified-by	`JAC-ACT-09`	current
`JAC-CLM-09`	reviewed-by	`JAC-ROLE-09`	current
`JAC-CLM-09`	reviewed-by	`JAC-ROLE-10`	current
`JAC-CLM-09`	reviewed-by	`JAC-ROLE-16`	current
`JAC-CLM-10`	evaluates	`JAC-DIM-10`	current
`JAC-CLM-10`	supported-by	`JAC-EVD-10`	current
`JAC-CLM-10`	verified-by	`JAC-ACT-10`	current
`JAC-CLM-10`	reviewed-by	`JAC-ROLE-10`	current
`JAC-CLM-10`	reviewed-by	`JAC-ROLE-15`	current
`JAC-CLM-10`	reviewed-by	`JAC-ROLE-16`	current
`JAC-CLM-11`	evaluates	`JAC-DIM-11`	current
`JAC-CLM-11`	supported-by	`JAC-EVD-11`	current
`JAC-CLM-11`	verified-by	`JAC-ACT-11`	current
`JAC-CLM-11`	reviewed-by	`JAC-ROLE-11`	current
`JAC-CLM-11`	reviewed-by	`JAC-ROLE-10`	current
`JAC-CLM-11`	reviewed-by	`JAC-ROLE-16`	current
`JAC-CLM-12`	evaluates	`JAC-DIM-12`	current
`JAC-CLM-12`	supported-by	`JAC-EVD-12`	current
`JAC-CLM-12`	verified-by	`JAC-ACT-12`	current
`JAC-CLM-12`	reviewed-by	`JAC-ROLE-12`	current
`JAC-CLM-12`	reviewed-by	`JAC-ROLE-16`	current
`JAC-CLM-12`	reviewed-by	`JAC-ROLE-17`	current
`JAC-CLM-13`	evaluates	`JAC-DIM-13`	current
`JAC-CLM-13`	supported-by	`JAC-EVD-13`	current
`JAC-CLM-13`	verified-by	`JAC-ACT-13`	current
`JAC-CLM-13`	reviewed-by	`JAC-ROLE-13`	current
`JAC-CLM-13`	reviewed-by	`JAC-ROLE-18`	current
`JAC-CLM-13`	reviewed-by	`JAC-ROLE-16`	current
`JAC-CLM-14`	evaluates	`JAC-DIM-14`	current
`JAC-CLM-14`	supported-by	`JAC-EVD-14`	current
`JAC-CLM-14`	verified-by	`JAC-ACT-14`	current
`JAC-CLM-14`	reviewed-by	`JAC-ROLE-14`	current
`JAC-CLM-14`	reviewed-by	`JAC-ROLE-03`	current
`JAC-CLM-14`	reviewed-by	`JAC-ROLE-17`	current
`JAC-CLM-15`	evaluates	`JAC-DIM-15`	current
`JAC-CLM-15`	supported-by	`JAC-EVD-15`	current
`JAC-CLM-15`	verified-by	`JAC-ACT-15`	current
`JAC-CLM-15`	reviewed-by	`JAC-ROLE-15`	current
`JAC-CLM-15`	reviewed-by	`JAC-ROLE-10`	current
`JAC-CLM-15`	reviewed-by	`JAC-ROLE-16`	current
`JAC-CLM-16`	evaluates	`JAC-DIM-16`	current
`JAC-CLM-16`	supported-by	`JAC-EVD-16`	current
`JAC-CLM-16`	verified-by	`JAC-ACT-16`	current
`JAC-CLM-16`	reviewed-by	`JAC-ROLE-16`	current
`JAC-CLM-16`	reviewed-by	`JAC-ROLE-17`	current
`JAC-CLM-16`	reviewed-by	`JAC-ROLE-18`	current

Public and operational boundary

This fixed teaching lab does not inspect or approve a real system.

It accepts no real architecture, inventory, log, evidence package, software artifact, model, SBOM, certificate, key, authority instrument, organization, person, mission, incident, target, weapon, coordinate, route, range, payload, signature, waveform, credential, private information, file, or arbitrary URL.

No real-system, legal, force, certification, accreditation, readiness, safety, compliance, or deployment determination was made. Real-system evidence reconstruction, exact artifact identity, authority reconstruction, human-interface evidence, and failure-origin analysis remain separately governed Evulgare responsibilities.

Direct answers

JADC2 assurance coverage questions

What is assurance evidence coverage?

It is the declared evidence showing which consequential conditions, intervals, dependencies, versions, authority states, human-review conditions, outcomes, and recovery states were actually observed within stated limits.

Why is no alert not evidence that no failure occurred?

A source, monitor, alert path, clock, retention system, or operator may have been unavailable. Without monitor-health and blind-period evidence, silence cannot distinguish a healthy system from an unobserved failure.

What is a monitor common-mode failure?

It occurs when the monitor shares the code, data, identity, administrator, infrastructure, power, time, or verification defect it is expected to detect, allowing both monitored function and monitor to fail together.

Can missing-period evidence be recovered after monitoring returns?

Not automatically. Restored monitoring can observe future conditions, but it cannot recreate evidence that was never collected during the blind interval unless an independent source preserved it.

Does a complete coverage graph certify JADC2 or CJADC2?

No. A graph makes declared coverage and blind spots inspectable. It does not establish real-system safety, readiness, legality, command authority, force authorization, certification, accreditation, or deployment approval.

Can this lab ingest real system logs or send evidence to Evulgare?

No. It accepts only one allowlisted fictional case and change. It performs no upload, external request, evidence transfer, artifact verification, real-system assessment, or server-side retention.