When evidence ages or the system changes
JADC2 Assurance Evidence Renewal and Continuous Re-Verification Lab
Compare six fixed fictional Joint All-Domain Command and Control mission-thread assurance cases and examine whether their evidence remains current after expiry, artifact changes, schema changes, source corrections, distribution drift, supplier changes, authority changes, human-review changes, and monitoring gaps.
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
Evidence does not remain current forever
A passing historical test is not permanent current support.
JADC2 means Joint All-Domain Command and Control. CJADC2 means Combined Joint All-Domain Command and Control. A kill chain is one selected ordered mission process; a kill web is the changing graph of possible mission threads; JADC2 or CJADC2 is the wider enterprise that enables, secures, governs, tests, and sustains those threads.
Evidence age and evidence relevance are different. A young record can already be stale after a material change, while an older record may remain useful as history without supporting a current claim. Scheduled retesting and event-triggered re-verification therefore remain separate obligations.
Governing definitions
Keep historical evidence, current support, scheduled renewal, and event-triggered re-verification separate.
Sixteen independent renewal dimensions
Every current claim remains tied to exact artifacts, assumptions, validity windows, change triggers, monitoring, evidence generation, and independent review.
JAR-DIM-01
Evidence creation time and validity period
Whether the evidence was generated within its declared time window and has not expired.
Renewal prerequisite: Generate current evidence for the exact declared scope, then complete independent review.
Expiry rule: Renew at the declared expiry or after a validity-triggering change.
Containment: Suspend dependent current claims until the dimension is renewed or explicitly withdrawn.
JAR-DIM-02
Exact artifact and policy version
Whether evidence refers to the exact software, model, configuration, schema, and policy currently under consideration.
Renewal prerequisite: Generate current evidence for the exact declared scope, then complete independent review.
Expiry rule: Expire after any relevant software, model, configuration, schema, or policy change.
Containment: Suspend dependent current claims until the dimension is renewed or explicitly withdrawn.
JAR-DIM-03
Source and transformation provenance
Whether source identity, custody, transformations, corrections, and derivations remain complete and authentic.
Renewal prerequisite: Generate current evidence for the exact declared scope, then complete independent review.
Expiry rule: Re-verify after any source correction, transformation change, custody gap, or lineage loss.
Containment: Suspend dependent current claims until the dimension is renewed or explicitly withdrawn.
JAR-DIM-04
Test environment and operating-assumption equivalence
Whether the renewed test reproduces the relevant load, timing, failure, environmental, and organizational assumptions.
Renewal prerequisite: Generate current evidence for the exact declared scope, then complete independent review.
Expiry rule: Expire when operating assumptions, workload, environment, mission bounds, or failure hypotheses change.
Containment: Suspend dependent current claims until the dimension is renewed or explicitly withdrawn.
JAR-DIM-05
Data freshness, calibration, and distribution drift
Whether data remain fresh, calibrated, representative, and inside the evaluated distribution.
Renewal prerequisite: Generate current evidence for the exact declared scope, then complete independent review.
Expiry rule: Re-evaluate continuously and after calibration, source-population, or distribution changes.
Containment: Suspend dependent current claims until the dimension is renewed or explicitly withdrawn.
JAR-DIM-06
Identity, signing, builder, and attestation validity
Whether artifact identity, builder identity, signatures, signing roots, and attestations remain current and independently verifiable.
Renewal prerequisite: Generate current evidence for the exact declared scope, then complete independent review.
Expiry rule: Expire on builder, signing-root, key, attestation-policy, or recovery change.
Containment: Suspend dependent current claims until the dimension is renewed or explicitly withdrawn.
JAR-DIM-07
Authority, delegation, purpose, expiry, and revocation
Whether the current evidence is used within a valid, unexpired, unrevoked, and purpose-bounded authority state.
Renewal prerequisite: Generate current evidence for the exact declared scope, then complete independent review.
Expiry rule: Re-check on every authority, delegation, purpose, expiry, revocation, or scope change.
Containment: Suspend dependent current claims until the dimension is renewed or explicitly withdrawn.
JAR-DIM-08
Human-review competence and practical conditions
Whether the reviewer remains independent, competent, informed, within workload limits, and able to inspect and challenge the evidence.
Renewal prerequisite: Generate current evidence for the exact declared scope, then complete independent review.
Expiry rule: Expire when reviewer role, competence, independence, evidence access, workload, or available time changes.
Containment: Suspend dependent current claims until the dimension is renewed or explicitly withdrawn.
JAR-DIM-09
Supplier, library, hardware, and service changes
Whether supplier, library, hardware, maintenance, hosting, or service dependencies remain equivalent to the tested state.
Renewal prerequisite: Generate current evidence for the exact declared scope, then complete independent review.
Expiry rule: Re-verify after supplier, library, hardware, service, maintainer, or dependency change.
Containment: Suspend dependent current claims until the dimension is renewed or explicitly withdrawn.
JAR-DIM-10
Common-mode dependency and diversity evidence
Whether alternatives remain diverse and independent for the declared failure hypothesis.
Renewal prerequisite: Generate current evidence for the exact declared scope, then complete independent review.
Expiry rule: Expire when code, signing, identity, time, power, transport, supplier, review, or verification dependencies change.
Containment: Suspend dependent current claims until the dimension is renewed or explicitly withdrawn.
JAR-DIM-11
Monitoring coverage and blind periods
Whether monitoring, logging, alerting, retention, and health checks covered the relevant period without an unexplained gap.
Renewal prerequisite: Generate current evidence for the exact declared scope, then complete independent review.
Expiry rule: Re-open after any blind period, disabled telemetry, retention gap, alert failure, or unobserved interval.
Containment: Suspend dependent current claims until the dimension is renewed or explicitly withdrawn.
JAR-DIM-12
Contradictory evidence and unresolved defeaters
Whether new evidence, counterclaims, anomalies, and defeaters have been reviewed rather than filtered out.
Renewal prerequisite: Generate current evidence for the exact declared scope, then complete independent review.
Expiry rule: Re-open when new contradictory evidence, a source correction, or an unresolved defeater appears.
Containment: Suspend dependent current claims until the dimension is renewed or explicitly withdrawn.
JAR-DIM-13
Reconciliation after partition or disconnected operation
Whether divergent state, duplicate task ownership, authority, evidence, and versions were reconciled after reconnection.
Renewal prerequisite: Generate current evidence for the exact declared scope, then complete independent review.
Expiry rule: Re-verify after partition, disconnected operation, state divergence, or return of connectivity.
Containment: Suspend dependent current claims until the dimension is renewed or explicitly withdrawn.
JAR-DIM-14
Correction propagation through derived products and claims
Whether a source or transformation correction reached every dependent product, decision, claim, cache, and case.
Renewal prerequisite: Generate current evidence for the exact declared scope, then complete independent review.
Expiry rule: Remain open until propagation is evidenced across every declared dependency.
Containment: Suspend dependent current claims until the dimension is renewed or explicitly withdrawn.
JAR-DIM-15
Recurrence testing under repeated and compound conditions
Whether the claimed remediation survives repeated, varied, and compound conditions rather than one favorable rerun.
Renewal prerequisite: Generate current evidence for the exact declared scope, then complete independent review.
Expiry rule: Renew after remediation, environment change, or discovery of a related failure mode.
Containment: Suspend dependent current claims until the dimension is renewed or explicitly withdrawn.
JAR-DIM-16
Independent closure review and residual unknowns
Whether an independent reviewer examined the complete renewed evidence, unresolved unknowns, scope, and publication limits.
Renewal prerequisite: Generate current evidence for the exact declared scope, then complete independent review.
Expiry rule: Expire when material evidence, assumptions, authority, or scope changes after closure.
Containment: Suspend dependent current claims until the dimension is renewed or explicitly withdrawn.
Eighteen implementation, evidence, and review roles
Ownership and independence remain inspectable.
JAR-ROLE-01Evidence lifecycle owner
evidence role
Maintains creation time, declared validity, expiry triggers, renewal status, and preservation of historical evidence.
JAR-ROLE-02Software and model configuration custodian
implementation role
Maintains exact software, model, configuration, schema, and policy identities tied to each evidence record.
JAR-ROLE-03Source and transformation provenance steward
evidence role
Maintains source custody, transformations, corrections, lineage, and dependent derived-product records.
JAR-ROLE-04Test-environment equivalence owner
assurance role
Documents whether renewed testing reproduces the assumptions, constraints, loads, failures, and environmental conditions of the original claim.
JAR-ROLE-05Data calibration and drift steward
evidence role
Maintains freshness, calibration, representativeness, distribution-shift, and out-of-scope evidence.
JAR-ROLE-06Build, signing, and attestation authority
implementation role
Maintains builder identity, signatures, attestations, signing roots, and artifact-verification history.
JAR-ROLE-07Authority and permitted-purpose owner
governance role
Maintains delegation, scope, purpose, expiry, revocation, and the separation between evidence renewal and authority restoration.
JAR-ROLE-08Human merits-review owner
review role
Maintains reviewer competence, independence, evidence access, workload, available time, and practical intervention records.
JAR-ROLE-09Supplier and dependency steward
implementation role
Maintains supplier, library, hardware, service, maintenance, and dependency-change evidence.
JAR-ROLE-10Common-mode and diversity evidence owner
assurance role
Maintains evidence that claimed alternatives remain materially diverse and independent for the declared failure hypothesis.
JAR-ROLE-11Continuous monitoring owner
evidence role
Maintains sensor coverage, logging coverage, blind periods, alert health, retention, and monitoring limitations.
JAR-ROLE-12Defeater and contradiction reviewer
review role
Maintains contradictory evidence, unresolved doubts, defeaters, and evidence that weakens or suspends prior support.
JAR-ROLE-13Reconciliation and disconnected-operation owner
implementation role
Maintains partition history, state divergence, reconciliation evidence, and return-of-control conditions.
JAR-ROLE-14Correction-propagation owner
evidence role
Tracks corrections through transformations, data products, decisions, claims, caches, and dependent cases.
JAR-ROLE-15Recurrence-test lead
verification role
Designs repeated and compound tests that challenge whether the original failure can recur under varied conditions.
JAR-ROLE-16Independent closure reviewer
review role
Reviews renewal evidence outside the originating implementation and evidence-generation chain before closure.
JAR-ROLE-17Portfolio assurance owner
governance role
Maintains dependent claim and case state without turning current evidence into permanent certification.
JAR-ROLE-18Residual-unknowns and publication reviewer
review role
Preserves unresolved uncertainty, publication boundaries, public-safe wording, and the separation between publication and operational authority.
Sixteen distinctions
Do not turn labels, copies, or repeated checks into assurance theater.
Six fixed fictional JADC2 assurance families
The renewal model preserves accepted case, portfolio, replay, and assurance identifiers while evaluating current evidence separately from the historical record.
It does not create a competing mission-thread catalog. Each case links to bounded renewal claims, evidence, verification activities, review roles, validity rules, and change triggers.
JAR-CASE-01 · JAP-CASE-01
Disaster-response information routing
A fictional multi-organization network routes infrastructure-damage observations to a bounded coordination service.
- Domain
- Joint emergency support
- Renewal dimensions
- 12
- Evidence links
- 12
JAR-CASE-02 · JAP-CASE-02
Infrastructure-protection coordination
A fictional protective network coordinates sensor, maintenance, and service-continuity information without modeling force.
- Domain
- Critical infrastructure protection
- Renewal dimensions
- 11
- Evidence links
- 11
JAR-CASE-03 · JAP-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
- Renewal dimensions
- 12
- Evidence links
- 12
JAR-CASE-04 · JAP-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
- Renewal dimensions
- 10
- Evidence links
- 10
JAR-CASE-05 · JAP-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
- Renewal dimensions
- 12
- Evidence links
- 12
JAR-CASE-06 · JAP-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
- Renewal dimensions
- 16
- Evidence links
- 16
Eight conservative renewal postures
Postures describe evidence currency, re-verification, authority, monitoring, and closure state; they never certify a portfolio.
The fixed fictional evidence remains current only for the exact artifacts, assumptions, authority, monitoring coverage, review conditions, and expiry recorded in the catalog.
One or more evidence records have exceeded their declared validity period. Historical support remains visible, but current reliance is suspended until the evidence is regenerated and independently reviewed.
Software, model, configuration, schema, signing, builder, supplier, or dependency state changed. Evidence tied to the previous artifact cannot be assumed equivalent.
The operating assumptions, data distribution, transformation lineage, reconciliation state, or correction propagation no longer match the conditions under which the original evidence was generated.
Authority, permitted purpose, delegation, reviewer competence, independence, evidence access, or workload conditions changed. Evidence renewal alone cannot restore authority or meaningful review.
A blind period or missing observation prevents the absence of alerts from being treated as evidence that no failure occurred.
A renewal was requested or partially performed, but prerequisites, correction propagation, recurrence testing, independent review, or dependent end-to-end evidence remain incomplete.
Unverified or incomplete renewal evidence was promoted into governance. The renewed claim and dependent decisions must be withdrawn until evidence and independent review are restored.
The fixed fictional evidence remains current only within its exact declared validity, artifact, assumption, authority, monitoring, review, and dependency bounds.
No composite renewal, confidence, readiness, safety, authority, diversity, legal, compliance, mission-success, certification, accreditation, or deployment score is calculated.
Containment
- Maintain the standing bounded-monitoring posture.
Required actions
- Monitor validity periods and every declared material-change trigger.
Renewal prerequisites
- Preserve exact artifact, assumption, authority, monitoring, and review context.
Required reviewers
JAR-ROLE-01Evidence lifecycle owner — Maintains creation time, declared validity, expiry triggers, renewal status, and preservation of historical evidence.JAR-ROLE-16Independent closure reviewer — Reviews renewal evidence outside the originating implementation and evidence-generation chain before closure.JAR-ROLE-17Portfolio assurance owner — Maintains dependent claim and case state without turning current evidence into permanent certification.
Warnings
- Current evidence is not permanent certification, readiness, authority, or operational permission.
Residual unknowns
- The public synthetic catalog cannot establish real-system behavior or hidden dependencies.
- The fixed public renewal graph cannot establish real-system safety, readiness, legal permission, command authority, certification, accreditation, force authorization, or deployment approval.
Dimension ledger
Original and current evidence-renewal state
| Dimension | Renewal prerequisite | Expiry rule | Original claim | Current claim | Evidence | Verification |
|---|---|---|---|---|---|---|
JAR-DIM-01Evidence creation time and validity period | Generate current evidence for the exact declared scope, then complete independent review. | Renew at the declared expiry or after a validity-triggering change. | qualified | qualified | current | current |
JAR-DIM-02Exact artifact and policy version | Generate current evidence for the exact declared scope, then complete independent review. | Expire after any relevant software, model, configuration, schema, or policy change. | qualified | qualified | current | current |
JAR-DIM-03Source and transformation provenance | Generate current evidence for the exact declared scope, then complete independent review. | Re-verify after any source correction, transformation change, custody gap, or lineage loss. | qualified | qualified | current | current |
JAR-DIM-04Test environment and operating-assumption equivalence | Generate current evidence for the exact declared scope, then complete independent review. | Expire when operating assumptions, workload, environment, mission bounds, or failure hypotheses change. | qualified | qualified | current | current |
JAR-DIM-05Data freshness, calibration, and distribution drift | Generate current evidence for the exact declared scope, then complete independent review. | Re-evaluate continuously and after calibration, source-population, or distribution changes. | qualified | qualified | current | current |
JAR-DIM-06Identity, signing, builder, and attestation validity | Generate current evidence for the exact declared scope, then complete independent review. | Expire on builder, signing-root, key, attestation-policy, or recovery change. | qualified | qualified | current | current |
JAR-DIM-07Authority, delegation, purpose, expiry, and revocation | Generate current evidence for the exact declared scope, then complete independent review. | Re-check on every authority, delegation, purpose, expiry, revocation, or scope change. | qualified | qualified | current | current |
JAR-DIM-08Human-review competence and practical conditions | Generate current evidence for the exact declared scope, then complete independent review. | Expire when reviewer role, competence, independence, evidence access, workload, or available time changes. | qualified | qualified | current | current |
JAR-DIM-09Supplier, library, hardware, and service changes | Generate current evidence for the exact declared scope, then complete independent review. | Re-verify after supplier, library, hardware, service, maintainer, or dependency change. | qualified | qualified | current | current |
JAR-DIM-10Common-mode dependency and diversity evidence | Generate current evidence for the exact declared scope, then complete independent review. | Expire when code, signing, identity, time, power, transport, supplier, review, or verification dependencies change. | qualified | qualified | current | current |
JAR-DIM-11Monitoring coverage and blind periods | Generate current evidence for the exact declared scope, then complete independent review. | Re-open after any blind period, disabled telemetry, retention gap, alert failure, or unobserved interval. | qualified | qualified | current | current |
JAR-DIM-12Contradictory evidence and unresolved defeaters | Generate current evidence for the exact declared scope, then complete independent review. | Re-open when new contradictory evidence, a source correction, or an unresolved defeater appears. | qualified | qualified | current | current |
JAR-DIM-13Reconciliation after partition or disconnected operation | Generate current evidence for the exact declared scope, then complete independent review. | Re-verify after partition, disconnected operation, state divergence, or return of connectivity. | qualified | qualified | current | current |
JAR-DIM-14Correction propagation through derived products and claims | Generate current evidence for the exact declared scope, then complete independent review. | Remain open until propagation is evidenced across every declared dependency. | qualified | qualified | current | current |
JAR-DIM-15Recurrence testing under repeated and compound conditions | Generate current evidence for the exact declared scope, then complete independent review. | Renew after remediation, environment change, or discovery of a related failure mode. | qualified | qualified | current | current |
JAR-DIM-16Independent closure review and residual unknowns | Generate current evidence for the exact declared scope, then complete independent review. | Expire when material evidence, assumptions, authority, or scope changes after closure. | qualified | qualified | current | current |
Transitive case impact
Dimension → claim → case → evidence → verification → review
| Case | Portfolio case | Original | Current | Affected dimensions | Evidence | Verification | Review roles |
|---|---|---|---|---|---|---|---|
JAR-CASE-01Disaster-response information routing | JAP-CASE-01 | qualified | qualified | 0 | 0 | 0 | 0 |
JAR-CASE-02Infrastructure-protection coordination | JAP-CASE-02 | qualified | qualified | 0 | 0 | 0 | 0 |
JAR-CASE-03Mission-partner awareness and releasability | JAP-CASE-03 | qualified | qualified | 0 | 0 | 0 | 0 |
JAR-CASE-04Logistics recovery after gateway loss | JAP-CASE-04 | qualified | qualified | 0 | 0 | 0 | 0 |
JAR-CASE-05Cyber-defense interpretation with contradictory evidence | JAP-CASE-05 | qualified | qualified | 0 | 0 | 0 | 0 |
JAR-CASE-06Time-critical protective support | JAP-CASE-06 | qualified | qualified | 0 | 0 | 0 | 0 |
Evidence ledger
Historical evidence remains visible when current, stale, expired, contradicted, suspended, or superseded
| Evidence | Dimension | Original | Current | Expiry | Limitation |
|---|---|---|---|---|---|
JAR-EV-01Evidence creation time and validity period evidence | validity-window | current | current | Renew at the declared expiry or after a validity-triggering change. | Expired evidence remains visible as history but cannot support a current claim. |
JAR-EV-02Exact artifact and policy version evidence | artifact-version | current | current | Expire after any relevant software, model, configuration, schema, or policy change. | A version label may not prove the deployed artifact or behavioral equivalence. |
JAR-EV-03Source and transformation provenance evidence | provenance-lineage | current | current | Re-verify after any source correction, transformation change, custody gap, or lineage loss. | A preserved file may still contain inaccurate or incompletely transformed evidence. |
JAR-EV-04Test environment and operating-assumption equivalence evidence | environment-equivalence | current | current | Expire when operating assumptions, workload, environment, mission bounds, or failure hypotheses change. | A repeated test may pass because the changed conditions were not reproduced. |
JAR-EV-05Data freshness, calibration, and distribution drift evidence | freshness-drift | current | current | Re-evaluate continuously and after calibration, source-population, or distribution changes. | No detected drift does not prove representativeness when monitoring coverage is incomplete. |
JAR-EV-06Identity, signing, builder, and attestation validity evidence | attestation-validity | current | current | Expire on builder, signing-root, key, attestation-policy, or recovery change. | A valid signature proves origin under a key, not equivalent behavior or operational permission. |
JAR-EV-07Authority, delegation, purpose, expiry, and revocation evidence | authority-purpose | current | current | Re-check on every authority, delegation, purpose, expiry, revocation, or scope change. | Evidence renewal cannot create, restore, or expand authority. |
JAR-EV-08Human-review competence and practical conditions evidence | human-review | current | current | Expire when reviewer role, competence, independence, evidence access, workload, or available time changes. | A named reviewer or click does not prove substantive judgment. |
JAR-EV-09Supplier, library, hardware, and service changes evidence | supplier-dependency | current | current | Re-verify after supplier, library, hardware, service, maintainer, or dependency change. | An unchanged application version may still depend on a changed underlying service or component. |
JAR-EV-10Common-mode dependency and diversity evidence evidence | diversity-evidence | current | current | Expire when code, signing, identity, time, power, transport, supplier, review, or verification dependencies change. | Additional paths do not prove additional failure-domain independence. |
JAR-EV-11Monitoring coverage and blind periods evidence | monitoring-coverage | current | current | Re-open after any blind period, disabled telemetry, retention gap, alert failure, or unobserved interval. | No alert during a blind period is not evidence that no failure occurred. |
JAR-EV-12Contradictory evidence and unresolved defeaters evidence | contradictory-evidence | current | current | Re-open when new contradictory evidence, a source correction, or an unresolved defeater appears. | Favorable evidence cannot average away a serious unresolved contradiction. |
JAR-EV-13Reconciliation after partition or disconnected operation evidence | reconciliation | current | current | Re-verify after partition, disconnected operation, state divergence, or return of connectivity. | Connection restoration is not state reconciliation or authority restoration. |
JAR-EV-14Correction propagation through derived products and claims evidence | correction-propagation | current | current | Remain open until propagation is evidenced across every declared dependency. | Correcting the source does not automatically correct every downstream copy or conclusion. |
JAR-EV-15Recurrence testing under repeated and compound conditions evidence | recurrence-testing | current | current | Renew after remediation, environment change, or discovery of a related failure mode. | One passing rerun is not evidence that recurrence has been prevented. |
JAR-EV-16Independent closure review and residual unknowns evidence | closure-unknowns | current | current | Expire when material evidence, assumptions, authority, or scope changes after closure. | Closure records do not eliminate residual unknowns or create permanent certification. |
Verification ledger
Scheduled retesting is not a substitute for event-triggered re-verification
| Verification | Dimension | Original | Current | Method | Independence requirement |
|---|---|---|---|---|---|
JAR-VER-01Renewal activity for evidence creation time and validity period | validity-window | current | current | Regenerate or re-check the fixed fictional evidence under current versions, assumptions, failure hypotheses, and review conditions. | The renewal must not rely only on the implementation, source, tool, dataset, reviewer, or authority whose validity is being assessed. |
JAR-VER-02Renewal activity for exact artifact and policy version | artifact-version | current | current | Regenerate or re-check the fixed fictional evidence under current versions, assumptions, failure hypotheses, and review conditions. | The renewal must not rely only on the implementation, source, tool, dataset, reviewer, or authority whose validity is being assessed. |
JAR-VER-03Renewal activity for source and transformation provenance | provenance-lineage | current | current | Regenerate or re-check the fixed fictional evidence under current versions, assumptions, failure hypotheses, and review conditions. | The renewal must not rely only on the implementation, source, tool, dataset, reviewer, or authority whose validity is being assessed. |
JAR-VER-04Renewal activity for test environment and operating-assumption equivalence | environment-equivalence | current | current | Regenerate or re-check the fixed fictional evidence under current versions, assumptions, failure hypotheses, and review conditions. | The renewal must not rely only on the implementation, source, tool, dataset, reviewer, or authority whose validity is being assessed. |
JAR-VER-05Renewal activity for data freshness, calibration, and distribution drift | freshness-drift | current | current | Regenerate or re-check the fixed fictional evidence under current versions, assumptions, failure hypotheses, and review conditions. | The renewal must not rely only on the implementation, source, tool, dataset, reviewer, or authority whose validity is being assessed. |
JAR-VER-06Renewal activity for identity, signing, builder, and attestation validity | attestation-validity | current | current | Regenerate or re-check the fixed fictional evidence under current versions, assumptions, failure hypotheses, and review conditions. | The renewal must not rely only on the implementation, source, tool, dataset, reviewer, or authority whose validity is being assessed. |
JAR-VER-07Renewal activity for authority, delegation, purpose, expiry, and revocation | authority-purpose | current | current | Regenerate or re-check the fixed fictional evidence under current versions, assumptions, failure hypotheses, and review conditions. | The renewal must not rely only on the implementation, source, tool, dataset, reviewer, or authority whose validity is being assessed. |
JAR-VER-08Renewal activity for human-review competence and practical conditions | human-review | current | current | Regenerate or re-check the fixed fictional evidence under current versions, assumptions, failure hypotheses, and review conditions. | The renewal must not rely only on the implementation, source, tool, dataset, reviewer, or authority whose validity is being assessed. |
JAR-VER-09Renewal activity for supplier, library, hardware, and service changes | supplier-dependency | current | current | Regenerate or re-check the fixed fictional evidence under current versions, assumptions, failure hypotheses, and review conditions. | The renewal must not rely only on the implementation, source, tool, dataset, reviewer, or authority whose validity is being assessed. |
JAR-VER-10Renewal activity for common-mode dependency and diversity evidence | diversity-evidence | current | current | Regenerate or re-check the fixed fictional evidence under current versions, assumptions, failure hypotheses, and review conditions. | The renewal must not rely only on the implementation, source, tool, dataset, reviewer, or authority whose validity is being assessed. |
JAR-VER-11Renewal activity for monitoring coverage and blind periods | monitoring-coverage | current | current | Regenerate or re-check the fixed fictional evidence under current versions, assumptions, failure hypotheses, and review conditions. | The renewal must not rely only on the implementation, source, tool, dataset, reviewer, or authority whose validity is being assessed. |
JAR-VER-12Renewal activity for contradictory evidence and unresolved defeaters | contradictory-evidence | current | current | Regenerate or re-check the fixed fictional evidence under current versions, assumptions, failure hypotheses, and review conditions. | The renewal must not rely only on the implementation, source, tool, dataset, reviewer, or authority whose validity is being assessed. |
JAR-VER-13Renewal activity for reconciliation after partition or disconnected operation | reconciliation | current | current | Regenerate or re-check the fixed fictional evidence under current versions, assumptions, failure hypotheses, and review conditions. | The renewal must not rely only on the implementation, source, tool, dataset, reviewer, or authority whose validity is being assessed. |
JAR-VER-14Renewal activity for correction propagation through derived products and claims | correction-propagation | current | current | Regenerate or re-check the fixed fictional evidence under current versions, assumptions, failure hypotheses, and review conditions. | The renewal must not rely only on the implementation, source, tool, dataset, reviewer, or authority whose validity is being assessed. |
JAR-VER-15Renewal activity for recurrence testing under repeated and compound conditions | recurrence-testing | current | current | Regenerate or re-check the fixed fictional evidence under current versions, assumptions, failure hypotheses, and review conditions. | The renewal must not rely only on the implementation, source, tool, dataset, reviewer, or authority whose validity is being assessed. |
JAR-VER-16Renewal activity for independent closure review and residual unknowns | closure-unknowns | current | current | Regenerate or re-check the fixed fictional evidence under current versions, assumptions, failure hypotheses, and review conditions. | The renewal must not rely only on the implementation, source, tool, dataset, reviewer, or authority whose validity is being assessed. |
Complete semantic renewal graph
Cases, renewal dimensions, claims, evidence, verification, roles, and dependencies
The graph is rendered as ordinary semantic tables. Affected current states are derived separately; the original graph remains visible and is never rewritten.
Inspect all 94 graph nodes
| Node ID | Type | Label | Imported source | Original state | Current state |
|---|---|---|---|---|---|
JAR-CASE-01 | renewal-case | Disaster-response information routing | JAD-CASE-01 | current | current |
JAD-CASE-01 | diversity-case | Imported diversity case JAD-CASE-01 | — | current | current |
JAR-CASE-02 | renewal-case | Infrastructure-protection coordination | JAD-CASE-02 | current | current |
JAD-CASE-02 | diversity-case | Imported diversity case JAD-CASE-02 | — | current | current |
JAR-CASE-03 | renewal-case | Mission-partner awareness and releasability | JAD-CASE-03 | current | current |
JAD-CASE-03 | diversity-case | Imported diversity case JAD-CASE-03 | — | current | current |
JAR-CASE-04 | renewal-case | Logistics recovery after gateway loss | JAD-CASE-04 | current | current |
JAD-CASE-04 | diversity-case | Imported diversity case JAD-CASE-04 | — | current | current |
JAR-CASE-05 | renewal-case | Cyber-defense interpretation with contradictory evidence | JAD-CASE-05 | current | current |
JAD-CASE-05 | diversity-case | Imported diversity case JAD-CASE-05 | — | current | current |
JAR-CASE-06 | renewal-case | Time-critical protective support | JAD-CASE-06 | current | current |
JAD-CASE-06 | diversity-case | Imported diversity case JAD-CASE-06 | — | current | current |
JAR-DIM-01 | renewal-dimension | Evidence creation time and validity period | — | current | current |
JAR-CLM-01 | renewal-claim | Current evidence claim: Evidence creation time and validity period | — | current | current |
JAR-DIM-02 | renewal-dimension | Exact artifact and policy version | — | current | current |
JAR-CLM-02 | renewal-claim | Current evidence claim: Exact artifact and policy version | — | current | current |
JAR-DIM-03 | renewal-dimension | Source and transformation provenance | — | current | current |
JAR-CLM-03 | renewal-claim | Current evidence claim: Source and transformation provenance | — | current | current |
JAR-DIM-04 | renewal-dimension | Test environment and operating-assumption equivalence | — | current | current |
JAR-CLM-04 | renewal-claim | Current evidence claim: Test environment and operating-assumption equivalence | — | current | current |
JAR-DIM-05 | renewal-dimension | Data freshness, calibration, and distribution drift | — | current | current |
JAR-CLM-05 | renewal-claim | Current evidence claim: Data freshness, calibration, and distribution drift | — | current | current |
JAR-DIM-06 | renewal-dimension | Identity, signing, builder, and attestation validity | — | current | current |
JAR-CLM-06 | renewal-claim | Current evidence claim: Identity, signing, builder, and attestation validity | — | current | current |
JAR-DIM-07 | renewal-dimension | Authority, delegation, purpose, expiry, and revocation | — | current | current |
JAR-CLM-07 | renewal-claim | Current evidence claim: Authority, delegation, purpose, expiry, and revocation | — | current | current |
JAR-DIM-08 | renewal-dimension | Human-review competence and practical conditions | — | current | current |
JAR-CLM-08 | renewal-claim | Current evidence claim: Human-review competence and practical conditions | — | current | current |
JAR-DIM-09 | renewal-dimension | Supplier, library, hardware, and service changes | — | current | current |
JAR-CLM-09 | renewal-claim | Current evidence claim: Supplier, library, hardware, and service changes | — | current | current |
JAR-DIM-10 | renewal-dimension | Common-mode dependency and diversity evidence | — | current | current |
JAR-CLM-10 | renewal-claim | Current evidence claim: Common-mode dependency and diversity evidence | — | current | current |
JAR-DIM-11 | renewal-dimension | Monitoring coverage and blind periods | — | current | current |
JAR-CLM-11 | renewal-claim | Current evidence claim: Monitoring coverage and blind periods | — | current | current |
JAR-DIM-12 | renewal-dimension | Contradictory evidence and unresolved defeaters | — | current | current |
JAR-CLM-12 | renewal-claim | Current evidence claim: Contradictory evidence and unresolved defeaters | — | current | current |
JAR-DIM-13 | renewal-dimension | Reconciliation after partition or disconnected operation | — | current | current |
JAR-CLM-13 | renewal-claim | Current evidence claim: Reconciliation after partition or disconnected operation | — | current | current |
JAR-DIM-14 | renewal-dimension | Correction propagation through derived products and claims | — | current | current |
JAR-CLM-14 | renewal-claim | Current evidence claim: Correction propagation through derived products and claims | — | current | current |
JAR-DIM-15 | renewal-dimension | Recurrence testing under repeated and compound conditions | — | current | current |
JAR-CLM-15 | renewal-claim | Current evidence claim: Recurrence testing under repeated and compound conditions | — | current | current |
JAR-DIM-16 | renewal-dimension | Independent closure review and residual unknowns | — | current | current |
JAR-CLM-16 | renewal-claim | Current evidence claim: Independent closure review and residual unknowns | — | current | current |
JAR-ROLE-01 | role | Evidence lifecycle owner | — | current | current |
JAR-ROLE-02 | role | Software and model configuration custodian | — | current | current |
JAR-ROLE-03 | role | Source and transformation provenance steward | — | current | current |
JAR-ROLE-04 | role | Test-environment equivalence owner | — | current | current |
JAR-ROLE-05 | role | Data calibration and drift steward | — | current | current |
JAR-ROLE-06 | role | Build, signing, and attestation authority | — | current | current |
JAR-ROLE-07 | role | Authority and permitted-purpose owner | — | current | current |
JAR-ROLE-08 | role | Human merits-review owner | — | current | current |
JAR-ROLE-09 | role | Supplier and dependency steward | — | current | current |
JAR-ROLE-10 | role | Common-mode and diversity evidence owner | — | current | current |
JAR-ROLE-11 | role | Continuous monitoring owner | — | current | current |
JAR-ROLE-12 | role | Defeater and contradiction reviewer | — | current | current |
JAR-ROLE-13 | role | Reconciliation and disconnected-operation owner | — | current | current |
JAR-ROLE-14 | role | Correction-propagation owner | — | current | current |
JAR-ROLE-15 | role | Recurrence-test lead | — | current | current |
JAR-ROLE-16 | role | Independent closure reviewer | — | current | current |
JAR-ROLE-17 | role | Portfolio assurance owner | — | current | current |
JAR-ROLE-18 | role | Residual-unknowns and publication reviewer | — | current | current |
JAR-EV-01 | evidence | Evidence creation time and validity period evidence | — | current | current |
JAR-EV-02 | evidence | Exact artifact and policy version evidence | — | current | current |
JAR-EV-03 | evidence | Source and transformation provenance evidence | — | current | current |
JAR-EV-04 | evidence | Test environment and operating-assumption equivalence evidence | — | current | current |
JAR-EV-05 | evidence | Data freshness, calibration, and distribution drift evidence | — | current | current |
JAR-EV-06 | evidence | Identity, signing, builder, and attestation validity evidence | — | current | current |
JAR-EV-07 | evidence | Authority, delegation, purpose, expiry, and revocation evidence | — | current | current |
JAR-EV-08 | evidence | Human-review competence and practical conditions evidence | — | current | current |
JAR-EV-09 | evidence | Supplier, library, hardware, and service changes evidence | — | current | current |
JAR-EV-10 | evidence | Common-mode dependency and diversity evidence evidence | — | current | current |
JAR-EV-11 | evidence | Monitoring coverage and blind periods evidence | — | current | current |
JAR-EV-12 | evidence | Contradictory evidence and unresolved defeaters evidence | — | current | current |
JAR-EV-13 | evidence | Reconciliation after partition or disconnected operation evidence | — | current | current |
JAR-EV-14 | evidence | Correction propagation through derived products and claims evidence | — | current | current |
JAR-EV-15 | evidence | Recurrence testing under repeated and compound conditions evidence | — | current | current |
JAR-EV-16 | evidence | Independent closure review and residual unknowns evidence | — | current | current |
JAR-VER-01 | verification | Renewal activity for evidence creation time and validity period | — | current | current |
JAR-VER-02 | verification | Renewal activity for exact artifact and policy version | — | current | current |
JAR-VER-03 | verification | Renewal activity for source and transformation provenance | — | current | current |
JAR-VER-04 | verification | Renewal activity for test environment and operating-assumption equivalence | — | current | current |
JAR-VER-05 | verification | Renewal activity for data freshness, calibration, and distribution drift | — | current | current |
JAR-VER-06 | verification | Renewal activity for identity, signing, builder, and attestation validity | — | current | current |
JAR-VER-07 | verification | Renewal activity for authority, delegation, purpose, expiry, and revocation | — | current | current |
JAR-VER-08 | verification | Renewal activity for human-review competence and practical conditions | — | current | current |
JAR-VER-09 | verification | Renewal activity for supplier, library, hardware, and service changes | — | current | current |
JAR-VER-10 | verification | Renewal activity for common-mode dependency and diversity evidence | — | current | current |
JAR-VER-11 | verification | Renewal activity for monitoring coverage and blind periods | — | current | current |
JAR-VER-12 | verification | Renewal activity for contradictory evidence and unresolved defeaters | — | current | current |
JAR-VER-13 | verification | Renewal activity for reconciliation after partition or disconnected operation | — | current | current |
JAR-VER-14 | verification | Renewal activity for correction propagation through derived products and claims | — | current | current |
JAR-VER-15 | verification | Renewal activity for recurrence testing under repeated and compound conditions | — | current | current |
JAR-VER-16 | verification | Renewal activity for independent closure review and residual unknowns | — | current | current |
Inspect all 175 graph relationships
| From | Relationship | To | Original state | Current state |
|---|---|---|---|---|
JAR-CASE-01 | imports-stable-case | JAD-CASE-01 | current | current |
JAR-CASE-01 | requires-current-claim | JAR-CLM-01 | current | current |
JAR-CASE-01 | requires-current-claim | JAR-CLM-02 | current | current |
JAR-CASE-01 | requires-current-claim | JAR-CLM-03 | current | current |
JAR-CASE-01 | requires-current-claim | JAR-CLM-04 | current | current |
JAR-CASE-01 | requires-current-claim | JAR-CLM-05 | current | current |
JAR-CASE-01 | requires-current-claim | JAR-CLM-06 | current | current |
JAR-CASE-01 | requires-current-claim | JAR-CLM-07 | current | current |
JAR-CASE-01 | requires-current-claim | JAR-CLM-08 | current | current |
JAR-CASE-01 | requires-current-claim | JAR-CLM-11 | current | current |
JAR-CASE-01 | requires-current-claim | JAR-CLM-12 | current | current |
JAR-CASE-01 | requires-current-claim | JAR-CLM-14 | current | current |
JAR-CASE-01 | requires-current-claim | JAR-CLM-16 | current | current |
JAR-CASE-02 | imports-stable-case | JAD-CASE-02 | current | current |
JAR-CASE-02 | requires-current-claim | JAR-CLM-01 | current | current |
JAR-CASE-02 | requires-current-claim | JAR-CLM-02 | current | current |
JAR-CASE-02 | requires-current-claim | JAR-CLM-03 | current | current |
JAR-CASE-02 | requires-current-claim | JAR-CLM-04 | current | current |
JAR-CASE-02 | requires-current-claim | JAR-CLM-05 | current | current |
JAR-CASE-02 | requires-current-claim | JAR-CLM-06 | current | current |
JAR-CASE-02 | requires-current-claim | JAR-CLM-09 | current | current |
JAR-CASE-02 | requires-current-claim | JAR-CLM-11 | current | current |
JAR-CASE-02 | requires-current-claim | JAR-CLM-12 | current | current |
JAR-CASE-02 | requires-current-claim | JAR-CLM-15 | current | current |
JAR-CASE-02 | requires-current-claim | JAR-CLM-16 | current | current |
JAR-CASE-03 | imports-stable-case | JAD-CASE-03 | current | current |
JAR-CASE-03 | requires-current-claim | JAR-CLM-01 | current | current |
JAR-CASE-03 | requires-current-claim | JAR-CLM-02 | current | current |
JAR-CASE-03 | requires-current-claim | JAR-CLM-03 | current | current |
JAR-CASE-03 | requires-current-claim | JAR-CLM-05 | current | current |
JAR-CASE-03 | requires-current-claim | JAR-CLM-06 | current | current |
JAR-CASE-03 | requires-current-claim | JAR-CLM-07 | current | current |
JAR-CASE-03 | requires-current-claim | JAR-CLM-08 | current | current |
JAR-CASE-03 | requires-current-claim | JAR-CLM-09 | current | current |
JAR-CASE-03 | requires-current-claim | JAR-CLM-10 | current | current |
JAR-CASE-03 | requires-current-claim | JAR-CLM-11 | current | current |
JAR-CASE-03 | requires-current-claim | JAR-CLM-14 | current | current |
JAR-CASE-03 | requires-current-claim | JAR-CLM-16 | current | current |
JAR-CASE-04 | imports-stable-case | JAD-CASE-04 | current | current |
JAR-CASE-04 | requires-current-claim | JAR-CLM-01 | current | current |
JAR-CASE-04 | requires-current-claim | JAR-CLM-02 | current | current |
JAR-CASE-04 | requires-current-claim | JAR-CLM-04 | current | current |
JAR-CASE-04 | requires-current-claim | JAR-CLM-09 | current | current |
JAR-CASE-04 | requires-current-claim | JAR-CLM-10 | current | current |
JAR-CASE-04 | requires-current-claim | JAR-CLM-11 | current | current |
JAR-CASE-04 | requires-current-claim | JAR-CLM-13 | current | current |
JAR-CASE-04 | requires-current-claim | JAR-CLM-14 | current | current |
JAR-CASE-04 | requires-current-claim | JAR-CLM-15 | current | current |
JAR-CASE-04 | requires-current-claim | JAR-CLM-16 | current | current |
JAR-CASE-05 | imports-stable-case | JAD-CASE-05 | current | current |
JAR-CASE-05 | requires-current-claim | JAR-CLM-01 | current | current |
JAR-CASE-05 | requires-current-claim | JAR-CLM-02 | current | current |
JAR-CASE-05 | requires-current-claim | JAR-CLM-03 | current | current |
JAR-CASE-05 | requires-current-claim | JAR-CLM-05 | current | current |
JAR-CASE-05 | requires-current-claim | JAR-CLM-06 | current | current |
JAR-CASE-05 | requires-current-claim | JAR-CLM-09 | current | current |
JAR-CASE-05 | requires-current-claim | JAR-CLM-10 | current | current |
JAR-CASE-05 | requires-current-claim | JAR-CLM-11 | current | current |
JAR-CASE-05 | requires-current-claim | JAR-CLM-12 | current | current |
JAR-CASE-05 | requires-current-claim | JAR-CLM-13 | current | current |
JAR-CASE-05 | requires-current-claim | JAR-CLM-15 | current | current |
JAR-CASE-05 | requires-current-claim | JAR-CLM-16 | current | current |
JAR-CASE-06 | imports-stable-case | JAD-CASE-06 | current | current |
JAR-CASE-06 | requires-current-claim | JAR-CLM-01 | current | current |
JAR-CASE-06 | requires-current-claim | JAR-CLM-02 | current | current |
JAR-CASE-06 | requires-current-claim | JAR-CLM-03 | current | current |
JAR-CASE-06 | requires-current-claim | JAR-CLM-04 | current | current |
JAR-CASE-06 | requires-current-claim | JAR-CLM-05 | current | current |
JAR-CASE-06 | requires-current-claim | JAR-CLM-06 | current | current |
JAR-CASE-06 | requires-current-claim | JAR-CLM-07 | current | current |
JAR-CASE-06 | requires-current-claim | JAR-CLM-08 | current | current |
JAR-CASE-06 | requires-current-claim | JAR-CLM-09 | current | current |
JAR-CASE-06 | requires-current-claim | JAR-CLM-10 | current | current |
JAR-CASE-06 | requires-current-claim | JAR-CLM-11 | current | current |
JAR-CASE-06 | requires-current-claim | JAR-CLM-12 | current | current |
JAR-CASE-06 | requires-current-claim | JAR-CLM-13 | current | current |
JAR-CASE-06 | requires-current-claim | JAR-CLM-14 | current | current |
JAR-CASE-06 | requires-current-claim | JAR-CLM-15 | current | current |
JAR-CASE-06 | requires-current-claim | JAR-CLM-16 | current | current |
JAR-CLM-01 | evaluates-currentness-of | JAR-DIM-01 | current | current |
JAR-CLM-01 | requires-role | JAR-ROLE-01 | current | review-required |
JAR-CLM-01 | requires-role | JAR-ROLE-16 | current | review-required |
JAR-CLM-01 | requires-role | JAR-ROLE-17 | current | review-required |
JAR-CLM-01 | supported-by | JAR-EV-01 | current | current |
JAR-CLM-01 | renewed-by | JAR-VER-01 | current | current |
JAR-CLM-02 | evaluates-currentness-of | JAR-DIM-02 | current | current |
JAR-CLM-02 | requires-role | JAR-ROLE-02 | current | current |
JAR-CLM-02 | requires-role | JAR-ROLE-06 | current | current |
JAR-CLM-02 | requires-role | JAR-ROLE-16 | current | review-required |
JAR-CLM-02 | supported-by | JAR-EV-02 | current | current |
JAR-CLM-02 | renewed-by | JAR-VER-02 | current | current |
JAR-CLM-03 | evaluates-currentness-of | JAR-DIM-03 | current | current |
JAR-CLM-03 | requires-role | JAR-ROLE-03 | current | current |
JAR-CLM-03 | requires-role | JAR-ROLE-14 | current | current |
JAR-CLM-03 | requires-role | JAR-ROLE-16 | current | review-required |
JAR-CLM-03 | supported-by | JAR-EV-03 | current | current |
JAR-CLM-03 | renewed-by | JAR-VER-03 | current | current |
JAR-CLM-04 | evaluates-currentness-of | JAR-DIM-04 | current | current |
JAR-CLM-04 | requires-role | JAR-ROLE-04 | current | current |
JAR-CLM-04 | requires-role | JAR-ROLE-15 | current | current |
JAR-CLM-04 | requires-role | JAR-ROLE-16 | current | review-required |
JAR-CLM-04 | supported-by | JAR-EV-04 | current | current |
JAR-CLM-04 | renewed-by | JAR-VER-04 | current | current |
JAR-CLM-05 | evaluates-currentness-of | JAR-DIM-05 | current | current |
JAR-CLM-05 | requires-role | JAR-ROLE-05 | current | current |
JAR-CLM-05 | requires-role | JAR-ROLE-11 | current | current |
JAR-CLM-05 | requires-role | JAR-ROLE-12 | current | current |
JAR-CLM-05 | supported-by | JAR-EV-05 | current | current |
JAR-CLM-05 | renewed-by | JAR-VER-05 | current | current |
JAR-CLM-06 | evaluates-currentness-of | JAR-DIM-06 | current | current |
JAR-CLM-06 | requires-role | JAR-ROLE-06 | current | current |
JAR-CLM-06 | requires-role | JAR-ROLE-02 | current | current |
JAR-CLM-06 | requires-role | JAR-ROLE-16 | current | review-required |
JAR-CLM-06 | supported-by | JAR-EV-06 | current | current |
JAR-CLM-06 | renewed-by | JAR-VER-06 | current | current |
JAR-CLM-07 | evaluates-currentness-of | JAR-DIM-07 | current | current |
JAR-CLM-07 | requires-role | JAR-ROLE-07 | current | current |
JAR-CLM-07 | requires-role | JAR-ROLE-17 | current | review-required |
JAR-CLM-07 | requires-role | JAR-ROLE-18 | current | current |
JAR-CLM-07 | supported-by | JAR-EV-07 | current | current |
JAR-CLM-07 | renewed-by | JAR-VER-07 | current | current |
JAR-CLM-08 | evaluates-currentness-of | JAR-DIM-08 | current | current |
JAR-CLM-08 | requires-role | JAR-ROLE-08 | current | current |
JAR-CLM-08 | requires-role | JAR-ROLE-12 | current | current |
JAR-CLM-08 | requires-role | JAR-ROLE-16 | current | review-required |
JAR-CLM-08 | supported-by | JAR-EV-08 | current | current |
JAR-CLM-08 | renewed-by | JAR-VER-08 | current | current |
JAR-CLM-09 | evaluates-currentness-of | JAR-DIM-09 | current | current |
JAR-CLM-09 | requires-role | JAR-ROLE-09 | current | current |
JAR-CLM-09 | requires-role | JAR-ROLE-02 | current | current |
JAR-CLM-09 | requires-role | JAR-ROLE-16 | current | review-required |
JAR-CLM-09 | supported-by | JAR-EV-09 | current | current |
JAR-CLM-09 | renewed-by | JAR-VER-09 | current | current |
JAR-CLM-10 | evaluates-currentness-of | JAR-DIM-10 | current | current |
JAR-CLM-10 | requires-role | JAR-ROLE-10 | current | current |
JAR-CLM-10 | requires-role | JAR-ROLE-09 | current | current |
JAR-CLM-10 | requires-role | JAR-ROLE-16 | current | review-required |
JAR-CLM-10 | supported-by | JAR-EV-10 | current | current |
JAR-CLM-10 | renewed-by | JAR-VER-10 | current | current |
JAR-CLM-11 | evaluates-currentness-of | JAR-DIM-11 | current | current |
JAR-CLM-11 | requires-role | JAR-ROLE-11 | current | current |
JAR-CLM-11 | requires-role | JAR-ROLE-01 | current | review-required |
JAR-CLM-11 | requires-role | JAR-ROLE-16 | current | review-required |
JAR-CLM-11 | supported-by | JAR-EV-11 | current | current |
JAR-CLM-11 | renewed-by | JAR-VER-11 | current | current |
JAR-CLM-12 | evaluates-currentness-of | JAR-DIM-12 | current | current |
JAR-CLM-12 | requires-role | JAR-ROLE-12 | current | current |
JAR-CLM-12 | requires-role | JAR-ROLE-16 | current | review-required |
JAR-CLM-12 | requires-role | JAR-ROLE-18 | current | current |
JAR-CLM-12 | supported-by | JAR-EV-12 | current | current |
JAR-CLM-12 | renewed-by | JAR-VER-12 | current | current |
JAR-CLM-13 | evaluates-currentness-of | JAR-DIM-13 | current | current |
JAR-CLM-13 | requires-role | JAR-ROLE-13 | current | current |
JAR-CLM-13 | requires-role | JAR-ROLE-07 | current | current |
JAR-CLM-13 | requires-role | JAR-ROLE-16 | current | review-required |
JAR-CLM-13 | supported-by | JAR-EV-13 | current | current |
JAR-CLM-13 | renewed-by | JAR-VER-13 | current | current |
JAR-CLM-14 | evaluates-currentness-of | JAR-DIM-14 | current | current |
JAR-CLM-14 | requires-role | JAR-ROLE-14 | current | current |
JAR-CLM-14 | requires-role | JAR-ROLE-03 | current | current |
JAR-CLM-14 | requires-role | JAR-ROLE-17 | current | review-required |
JAR-CLM-14 | supported-by | JAR-EV-14 | current | current |
JAR-CLM-14 | renewed-by | JAR-VER-14 | current | current |
JAR-CLM-15 | evaluates-currentness-of | JAR-DIM-15 | current | current |
JAR-CLM-15 | requires-role | JAR-ROLE-15 | current | current |
JAR-CLM-15 | requires-role | JAR-ROLE-04 | current | current |
JAR-CLM-15 | requires-role | JAR-ROLE-16 | current | review-required |
JAR-CLM-15 | supported-by | JAR-EV-15 | current | current |
JAR-CLM-15 | renewed-by | JAR-VER-15 | current | current |
JAR-CLM-16 | evaluates-currentness-of | JAR-DIM-16 | current | current |
JAR-CLM-16 | requires-role | JAR-ROLE-16 | current | review-required |
JAR-CLM-16 | requires-role | JAR-ROLE-17 | current | review-required |
JAR-CLM-16 | requires-role | JAR-ROLE-18 | current | current |
JAR-CLM-16 | supported-by | JAR-EV-16 | current | current |
JAR-CLM-16 | renewed-by | JAR-VER-16 | current | current |
Evidence requiring renewal
- No evidence record is changed in the selected baseline state.
Verification to repeat or replace
- No additional verification is required in the selected baseline state.
JADC2 assurance evidence-renewal analysis loaded.
Direct answers
What evidence renewal can and cannot establish
Why does assurance evidence need renewal?
Evidence supports only the exact artifacts, assumptions, environment, authority, monitoring, and review conditions under which it was generated. Expiry or a material change can suspend current reliance even when the historical record remains intact.
Is scheduled retesting enough?
No. Scheduled retesting addresses age, while event-triggered re-verification addresses material changes such as new software, schemas, suppliers, authority, data distributions, review conditions, or monitoring gaps.
Does a valid signature prove the evidence is still relevant?
No. A signature can establish artifact identity or integrity. It does not establish behavioral equivalence, current environmental relevance, current authority, or current evidence sufficiency.
What happens to expired or invalidated evidence?
It remains visible as historical evidence with its original scope and validity. Dependent current claims are suspended, qualified, or withdrawn until replacement evidence and independent review are complete.
Does renewed evidence certify a JADC2 mission thread?
No. Renewal can restore bounded current support for declared claims. It does not establish real-system safety, readiness, legal compliance, command authority, force authorization, accreditation, certification, or deployment approval.
Can the lab ingest real evidence or connect to Evulgare?
No. The public lab accepts only one allowlisted fictional change. It performs no upload, artifact verification, external request, evidence transfer, real-system assessment, Evulgare integration, or server-side evidence retention.
Public synthetic boundary
The output is an evidence-currency and re-verification posture—not a real-system assessment.
The lab cannot accept or infer a real architecture, evidence package, software artifact, model, SBOM, certificate, key, supplier, organization, system, target, route, mission, or authority instrument. It cannot renew real evidence, optimize a portfolio, allocate weapons, calculate mission success, authorize force, determine legality, certify safety, approve deployment, or create an Evulgare project.
No composite score is calculated. A complete renewal graph makes declared validity and change relationships visible; it does not prove current safety, readiness, authority, or the absence of hidden invalidating changes.