KillWebs.comComposable mission networks

When apparent alternatives share hidden roots

JADC2 Assurance Portfolio Independence and Diversity Evidence Lab

Compare six fixed fictional Joint All-Domain Command and Control mission-thread assurance cases and test whether their apparent alternatives are truly diverse and independent across code, signing, updates, identity, time, power, transport, semantics, provenance, compute, administration, review, reconciliation, environment, and verification.

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

Diversity is a claim that requires evidence

Two paths are not automatically two failure domains.

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.

Redundancy means another instance, path, or capacity exists. Diversity means the alternative differs materially for a declared failure hypothesis. Independence means the alternatives do not share the relevant failure cause for that scope. Different names, vendors, regions, routes, or process IDs do not establish those properties.

Governing definitions

Keep sequence, option space, enterprise, redundancy, diversity, and independence separate.

jadc2Joint All-Domain Command and Control
cjadc2Combined Joint All-Domain Command and Control
kill chainOne selected ordered mission process.
kill webThe changing graph of possible mission threads.
redundancyAdditional capacity or another path.
diversityMeaningful implementation difference tied to a declared failure hypothesis.
independenceAbsence of a relevant shared failure cause for the stated scope.

Sixteen independent diversity dimensions

Every claim is tied to a failure hypothesis, evidence, verification, expiry, containment, and uncertainty.

JAD-DIM-01

Software or model code lineage

Whether claimed alternatives arise from materially different source, generated code, libraries, model families, and defect ancestry.

Failure hypothesis: One shared defect or inherited component can invalidate every apparently redundant implementation.

Imported dependencies: software-lineage, supply-chain

Expiry: Re-review after any source, generated-code, library, model, or compiler-input change.

JAD-DIM-02

Build pipeline and signing root

Whether alternatives use independently administered builds, signing roots, attestation paths, and key-recovery procedures.

Failure hypothesis: One compromised builder or signing root can make several distinct packages fail together.

Imported dependencies: software-lineage, update-rollback, supply-chain

Expiry: Expire on key rotation, builder change, attestation-policy change, or recovery event.

JAD-DIM-03

Package repository and update channel

Whether alternatives receive software, model, policy, and configuration changes through genuinely separate repositories and distribution controls.

Failure hypothesis: One compromised repository or promotion channel can distribute the same defect across every alternative.

Imported dependencies: update-rollback, supply-chain

Expiry: Re-review after repository, mirror, promotion, rollback, or distribution-policy changes.

JAD-DIM-04

Configuration-authoring authority

Whether settings, policy bundles, thresholds, and permitted-use rules have separate authoring and approval paths.

Failure hypothesis: One mistaken or compromised configuration authority can push the same unsafe state into otherwise diverse implementations.

Imported dependencies: software-lineage, policy-purpose, authority-record

Expiry: Expire on configuration-schema, policy-authority, approval-workflow, or delegation changes.

JAD-DIM-05

Identity provider and trust anchor

Whether alternative services rely on independent identity providers, trust anchors, administrators, and revocation paths.

Failure hypothesis: One compromised identity or trust-control plane can authorize or impersonate every alternative.

Imported dependencies: identity-trust

Expiry: Expire on trust-store, identity-provider, administrator, revocation, or authentication-policy change.

JAD-DIM-06

Trusted-time source and clock hardware

Whether alternatives rely on distinct physical references, clock hardware, synchronization paths, and holdover behavior.

Failure hypothesis: One manipulated reference can corrupt freshness, ordering, expiry, and reconciliation across multiple routes.

Imported dependencies: trusted-time

Expiry: Expire after reference, clock, synchronization, holdover, or drift-limit changes.

JAD-DIM-07

Power source and physical utility dependency

Whether regional alternatives avoid one power grid, facility, fuel, cooling, cable route, or utility administration.

Failure hypothesis: A single physical utility failure can remove services that appear geographically or logically separate.

Imported dependencies: compute-capacity, transport-domain, environment-assumption

Expiry: Re-review after facility, utility, backup-power, cooling, carrier, or regional-hosting changes.

JAD-DIM-08

Communications gateway and carrier path

Whether differently named paths use distinct gateways, carrier infrastructure, control planes, spectrum assumptions, and administrative ownership.

Failure hypothesis: One gateway, carrier, routing controller, or physical path can disable several apparent routes.

Imported dependencies: transport-domain

Expiry: Expire after gateway, route, carrier, controller, link-policy, or physical-path changes.

JAD-DIM-09

Semantic schema implementation and translator lineage

Whether alternatives interpret shared data through independently implemented semantics, translation logic, and test oracles.

Failure hypothesis: One semantic defect can cause every route to interpret the same field incorrectly even when transport succeeds.

Imported dependencies: semantic-schema, software-lineage, supply-chain

Expiry: Re-review after schema, translator, conformance-suite, or interpretation-policy changes.

JAD-DIM-10

Data-product source and provenance chain

Whether alternative evidence products derive from independent sources, collection paths, transformations, and correction processes.

Failure hypothesis: Several products can repeat one source and create false corroboration rather than independent evidence.

Imported dependencies: provenance

Expiry: Expire after source correction, custody gap, transformation change, evidence-age limit, or derived-product update.

JAD-DIM-11

Compute architecture and regional hosting dependency

Whether alternatives use independently managed compute, hypervisors, facilities, schedulers, and regional control planes.

Failure hypothesis: Different applications or regions can still fail together through one compute layer, scheduler, facility, or administrator.

Imported dependencies: compute-capacity, software-lineage, environment-assumption

Expiry: Re-review after hosting, hypervisor, scheduler, facility, regional-administration, or capacity changes.

JAD-DIM-12

Supplier, maintainer, and administrative ownership

Whether alternatives avoid one supplier, subcontractor, maintenance tool, remote administrator, and organizational control chain.

Failure hypothesis: One supplier defect or privileged administrative path can affect multiple apparently independent services.

Imported dependencies: supply-chain, software-lineage, identity-trust

Expiry: Expire on supplier, maintainer, subcontractor, remote-tool, privilege, or ownership changes.

JAD-DIM-13

Human-review pool and escalation chain

Whether reviews use independently accountable people, evidence access, supervision, incentives, escalation, and intervention capacity.

Failure hypothesis: Separate reviewer names can still produce one correlated decision chain, common workload failure, or procedural confirmation pattern.

Imported dependencies: human-review-pool, authority-record

Expiry: Expire after staffing, supervision, evidence-access, workload, authority, or escalation changes.

JAD-DIM-14

Assessment and reconciliation implementation

Whether alternatives use independent assessment logic, conflict handling, state reconciliation, and return-of-control mechanisms.

Failure hypothesis: One flawed assessment or reconciliation service can make every alternative agree on the same incorrect current state.

Imported dependencies: assessment-reconciliation, software-lineage

Expiry: Expire on assessment, state-merging, conflict-resolution, rollback, or return-of-control changes.

JAD-DIM-15

Operating-environment assumption

Whether alternatives remain meaningfully different under the same fictional disruption, load, evidence, timing, and environmental conditions.

Failure hypothesis: Diversity evidence collected under one benign assumption may not apply when the shared environment changes.

Imported dependencies: environment-assumption

Expiry: Expire when load, communications, timing, threat, data quality, environmental, or operating assumptions change materially.

JAD-DIM-16

Testing method, dataset, and verification-tool independence

Whether evidence comes from genuinely different methods, datasets, tools, oracles, teams, and failure hypotheses.

Failure hypothesis: Repeated tests can reproduce the same blind spot when they share a tool, model, dataset, oracle, or supervisory chain.

Imported dependencies: software-lineage, supply-chain, human-review-pool

Expiry: Re-review after verification-tool, model, dataset, oracle, reviewer, or test-design change.

Eighteen implementation, evidence, and review roles

Ownership and independence remain inspectable.

JAD-ROLE-01

Software lineage custodian

implementation role

Maintains fictional source, binary, model, library, and derivation records for claimed alternatives.

JAD-ROLE-02

Build and signing authority

implementation role

Maintains fictional build-pipeline, signing-root, attestation, and key-separation evidence.

JAD-ROLE-03

Repository and update-channel steward

implementation role

Maintains fictional package repositories, distribution paths, rollback records, and compromise windows.

JAD-ROLE-04

Configuration-authoring authority

governance role

Separates configuration ownership, review, approval, and propagation across alternatives.

JAD-ROLE-05

Identity and trust-anchor operator

implementation role

Maintains fictional identity-provider, workload-identity, trust-anchor, and administrative-control evidence.

JAD-ROLE-06

Trusted-time and clock steward

implementation role

Maintains fictional time-source, holdover-clock, synchronization, expiry, and physical-reference evidence.

JAD-ROLE-07

Power and utility dependency steward

implementation role

Maps fictional power, facility, carrier, and physical utility dependencies across regions.

JAD-ROLE-08

Transport and gateway steward

implementation role

Maintains fictional gateway, carrier, route, control-plane, and failure-domain evidence.

JAD-ROLE-09

Semantic translator maintainer

implementation role

Maintains fictional schema implementations, translation logic, conformance evidence, and defect history.

JAD-ROLE-10

Data-product and provenance steward

evidence role

Maintains fictional source lineage, custody, transformation, correction, and derived-product invalidation evidence.

JAD-ROLE-11

Compute and hosting steward

implementation role

Maps fictional processor, hypervisor, regional hosting, administration, and utility dependencies.

JAD-ROLE-12

Supplier and maintenance administrator

implementation role

Maintains fictional supplier, maintainer, remote-administration, tooling, and subcontractor relationships.

JAD-ROLE-13

Human merits-review pool owner

review role

Maintains reviewer independence, evidence access, workload, escalation, and intervention records.

JAD-ROLE-14

Assessment and reconciliation owner

evidence role

Maintains fictional outcome, reconciliation, conflict, and return-of-control evidence.

JAD-ROLE-15

Operating-environment assumption owner

assurance role

Maintains the environmental conditions and failure hypotheses under which diversity evidence remains relevant.

JAD-ROLE-16

Independent verification lead

review role

Selects genuinely different test methods, datasets, tools, and oracles and documents residual correlation.

JAD-ROLE-17

Portfolio assurance owner

governance role

Maintains the fixed portfolio graph without treating graph completeness as certification.

JAD-ROLE-18

Independent diversity and containment reviewer

review role

Reviews common-mode discoveries outside the original implementation and verification chains and coordinates containment.

Sixteen distinctions

Do not turn labels, copies, or repeated checks into assurance theater.

Two instancesTwo implementations
Different product namesDifferent code lineage
Different vendorsIndependent upstream dependency
Different regionsIndependent identity, time, power, or control plane
Separate processesSeparate failure domains
Separate certificatesSeparate signing root
Different routesIndependent gateway or carrier
Different schemasSemantically diverse interpretation
Separate reviewersIndependent evidence or decision chain
Repeated testIndependent verification method
Passing failoverCommon-mode resilience
Diverse implementationCurrent authority or permitted use
Contained faultContained derived-product impact
Evidence of independenceUniversal proof of independence
Complete diversity graphCertification or deployment approval
Restored alternativeReconciled portfolio state

Six imported fictional JADC2 assurance families

The diversity model references the accepted portfolio and assurance identifiers.

It does not create a competing mission-thread catalog. Each record imports the current portfolio case and links it to sixteen diversity claims, fixed evidence, verification, and abstract roles.

JAD-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
Diversity claims
16
Imported dependencies
15

JAD-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
Diversity claims
16
Imported dependencies
14

JAD-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
Diversity claims
16
Imported dependencies
15

JAD-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
Diversity claims
16
Imported dependencies
14

JAD-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
Diversity claims
16
Imported dependencies
13

JAD-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
Diversity claims
16
Imported dependencies
15

Eight conservative postures

Postures describe evidence and review state; they never certify the portfolio.

qualifiedDiversity evidence supportable within declared bounds

The fixed fictional portfolio contains current evidence for selected implementation differences, but every claim remains tied to a declared failure hypothesis, exact artifacts, expiry, and residual unknowns.

qualifiedDiversity claim requires qualification

One apparent alternative still differs in some dimensions, but a newly discovered common dependency narrows the claimed independence and requires more explicit qualification.

unresolvedImplementation independence unverified

The available fictional evidence does not establish that the alternatives avoid the same source, administrative, supervisory, or derived-product failure cause.

suspendedCommon code or update lineage detected

Two apparent alternatives share code, signing, repository, or update ancestry. Failover remains possible, but common-mode resilience cannot be claimed until the shared lineage is contained and re-verified.

suspendedShared trust or utility root detected

Different regions or services still depend on one identity control plane, time reference, power source, network utility, or administrative root.

suspendedVerification independence suspended

The supposedly independent tests share one model, dataset, oracle, tool, reviewer chain, or defect and therefore cannot independently support the diversity claim.

suspendedPortfolio containment and re-review required

A common implementation, update, semantic, provenance, or derived-product failure may affect several cases. Containment and independent re-review are required before the alternatives are treated as current.

withdrawnGovernance boundary exceeded

An unverified diversity claim was promoted into portfolio governance. The claim, dependent decisions, and derived assurance state must be withdrawn until evidence and independent review are restored.

Bounded diversity-evidence change

Stress one common-mode claim without rewriting the original record.

Synthetic only

Only allowlisted identifiers are accepted. No free-form architecture, code, artifact, evidence, key, file, URL, organization, mission, or target can be submitted.

Original postureDiversity evidence supportable within declared boundsqualified
Current postureDiversity evidence supportable within declared boundsqualified

The fixed fictional portfolio contains bounded evidence for implementation differences, but every claim remains tied to exact artifacts, failure hypotheses, expiry, and independent review.

No composite JADC2, diversity, independence, resilience, trust, evidence, verification, authority, review, readiness, safety, legality, mission-success, certification, or deployment score is calculated.

Cases affected0
Diversity dimensions affected0
Roles requiring review2
Evidence records affected0
Verification activities affected0
Certification or deployment approvalNo

Containment

  • Maintain the standing bounded-monitoring posture.

Required actions

  • Monitor artifact identity, expiry, ownership, dependency, review, and failure-hypothesis changes.

Expiry and renewal

  • Re-evaluate each claim at its declared expiry or when a linked artifact or assumption changes.

Required reviewers

  • JAD-ROLE-17 Portfolio assurance owner — Maintains the fixed portfolio graph without treating graph completeness as certification.
  • JAD-ROLE-18 Independent diversity and containment reviewer — Reviews common-mode discoveries outside the original implementation and verification chains and coordinates containment.

Warnings

  • Current fictional evidence is not universal proof, certification, readiness, authority, or real-system resilience.

Residual unknowns

  • The public catalog cannot reveal hidden real-system dependencies or operational behavior.
  • The fixed public diversity graph cannot establish real-system independence, operational resilience, legal permission, force authority, readiness, certification, or deployment approval.

Dimension ledger

Original and current diversity evidence

DimensionFailure hypothesisImported dependenciesOriginal claimCurrent claimEvidenceVerification
JAD-DIM-01
Software or model code lineage		One shared defect or inherited component can invalidate every apparently redundant implementation.software-lineage, supply-chainqualifiedqualifiedcurrentcurrent
JAD-DIM-02
Build pipeline and signing root		One compromised builder or signing root can make several distinct packages fail together.software-lineage, update-rollback, supply-chainqualifiedqualifiedcurrentcurrent
JAD-DIM-03
Package repository and update channel		One compromised repository or promotion channel can distribute the same defect across every alternative.update-rollback, supply-chainqualifiedqualifiedcurrentcurrent
JAD-DIM-04
Configuration-authoring authority		One mistaken or compromised configuration authority can push the same unsafe state into otherwise diverse implementations.software-lineage, policy-purpose, authority-recordqualifiedqualifiedcurrentcurrent
JAD-DIM-05
Identity provider and trust anchor		One compromised identity or trust-control plane can authorize or impersonate every alternative.identity-trustqualifiedqualifiedcurrentcurrent
JAD-DIM-06
Trusted-time source and clock hardware		One manipulated reference can corrupt freshness, ordering, expiry, and reconciliation across multiple routes.trusted-timequalifiedqualifiedcurrentcurrent
JAD-DIM-07
Power source and physical utility dependency		A single physical utility failure can remove services that appear geographically or logically separate.compute-capacity, transport-domain, environment-assumptionqualifiedqualifiedcurrentcurrent
JAD-DIM-08
Communications gateway and carrier path		One gateway, carrier, routing controller, or physical path can disable several apparent routes.transport-domainqualifiedqualifiedcurrentcurrent
JAD-DIM-09
Semantic schema implementation and translator lineage		One semantic defect can cause every route to interpret the same field incorrectly even when transport succeeds.semantic-schema, software-lineage, supply-chainqualifiedqualifiedcurrentcurrent
JAD-DIM-10
Data-product source and provenance chain		Several products can repeat one source and create false corroboration rather than independent evidence.provenancequalifiedqualifiedcurrentcurrent
JAD-DIM-11
Compute architecture and regional hosting dependency		Different applications or regions can still fail together through one compute layer, scheduler, facility, or administrator.compute-capacity, software-lineage, environment-assumptionqualifiedqualifiedcurrentcurrent
JAD-DIM-12
Supplier, maintainer, and administrative ownership		One supplier defect or privileged administrative path can affect multiple apparently independent services.supply-chain, software-lineage, identity-trustqualifiedqualifiedcurrentcurrent
JAD-DIM-13
Human-review pool and escalation chain		Separate reviewer names can still produce one correlated decision chain, common workload failure, or procedural confirmation pattern.human-review-pool, authority-recordqualifiedqualifiedcurrentcurrent
JAD-DIM-14
Assessment and reconciliation implementation		One flawed assessment or reconciliation service can make every alternative agree on the same incorrect current state.assessment-reconciliation, software-lineagequalifiedqualifiedcurrentcurrent
JAD-DIM-15
Operating-environment assumption		Diversity evidence collected under one benign assumption may not apply when the shared environment changes.environment-assumptionqualifiedqualifiedcurrentcurrent
JAD-DIM-16
Testing method, dataset, and verification-tool independence		Repeated tests can reproduce the same blind spot when they share a tool, model, dataset, oracle, or supervisory chain.software-lineage, supply-chain, human-review-poolqualifiedqualifiedcurrentcurrent

Transitive case impact

Dimension → imported dependency → case → evidence → verification

CaseImported portfolio caseOriginalCurrentAffected dimensionsEvidenceVerificationReview roles
JAD-CASE-01
Disaster-response information routing		JAP-CASE-01qualifiedqualified0000
JAD-CASE-02
Infrastructure-protection coordination		JAP-CASE-02qualifiedqualified0000
JAD-CASE-03
Mission-partner awareness and releasability		JAP-CASE-03qualifiedqualified0000
JAD-CASE-04
Logistics recovery after gateway loss		JAP-CASE-04qualifiedqualified0000
JAD-CASE-05
Cyber-defense interpretation with contradictory evidence		JAP-CASE-05qualifiedqualified0000
JAD-CASE-06
Time-critical protective support		JAP-CASE-06qualifiedqualified0000

Evidence ledger

Evidence remains visible when qualified, contradicted, correlated, or unverified

EvidenceDimensionOriginalCurrentExpiryLimitation
JAD-EV-01
Software or model code lineage evidence record		code-lineagecurrentcurrentRe-review after any source, generated-code, library, model, or compiler-input change.Undeclared transitive dependencies may still create common code ancestry.
JAD-EV-02
Build pipeline and signing root evidence record		build-signingcurrentcurrentExpire on key rotation, builder change, attestation-policy change, or recovery event.Separate certificates may still chain to one administrative or cryptographic root.
JAD-EV-03
Package repository and update channel evidence record		update-channelcurrentcurrentRe-review after repository, mirror, promotion, rollback, or distribution-policy changes.Independent mirrors may still depend on one origin or one administrator.
JAD-EV-04
Configuration-authoring authority evidence record		configuration-authoritycurrentcurrentExpire on configuration-schema, policy-authority, approval-workflow, or delegation changes.Separate files can still be generated by one policy compiler or supervisory chain.
JAD-EV-05
Identity provider and trust anchor evidence record		identity-trust-anchorcurrentcurrentExpire on trust-store, identity-provider, administrator, revocation, or authentication-policy change.Different namespaces may still be governed by one root administrator or recovery authority.
JAD-EV-06
Trusted-time source and clock hardware evidence record		trusted-timecurrentcurrentExpire after reference, clock, synchronization, holdover, or drift-limit changes.Different time services may still depend on one physical reference or facility.
JAD-EV-07
Power source and physical utility dependency evidence record		power-utilitycurrentcurrentRe-review after facility, utility, backup-power, cooling, carrier, or regional-hosting changes.Independent locations may share upstream generation, distribution, cooling, or physical access.
JAD-EV-08
Communications gateway and carrier path evidence record		transport-carriercurrentcurrentExpire after gateway, route, carrier, controller, link-policy, or physical-path changes.Apparently separate paths may converge at an undocumented gateway or carrier control plane.
JAD-EV-09
Semantic schema implementation and translator lineage evidence record		semantic-translatorcurrentcurrentRe-review after schema, translator, conformance-suite, or interpretation-policy changes.Different schemas can still encode the same flawed assumption or generated translator.
JAD-EV-10
Data-product source and provenance chain evidence record		data-provenancecurrentcurrentExpire after source correction, custody gap, transformation change, evidence-age limit, or derived-product update.Distinct products may share one upstream source, calibration, labeling process, or institutional origin.
JAD-EV-11
Compute architecture and regional hosting dependency evidence record		compute-hostingcurrentcurrentRe-review after hosting, hypervisor, scheduler, facility, regional-administration, or capacity changes.Separate regions can share one management plane, image, hypervisor, utility, or operator.
JAD-EV-12
Supplier, maintainer, and administrative ownership evidence record		supplier-administrationcurrentcurrentExpire on supplier, maintainer, subcontractor, remote-tool, privilege, or ownership changes.Different vendors may share one upstream supplier, maintainer, library, or support organization.
JAD-EV-13
Human-review pool and escalation chain evidence record		human-reviewcurrentcurrentExpire after staffing, supervision, evidence-access, workload, authority, or escalation changes.Nominally separate reviewers may share one supervisor, briefing, evidence package, or institutional incentive.
JAD-EV-14
Assessment and reconciliation implementation evidence record		assessment-reconciliationcurrentcurrentExpire on assessment, state-merging, conflict-resolution, rollback, or return-of-control changes.Different interfaces may still call one reconciliation engine or share one outcome oracle.
JAD-EV-15
Operating-environment assumption evidence record		environment-assumptioncurrentcurrentExpire when load, communications, timing, threat, data quality, environmental, or operating assumptions change materially.The public synthetic environment cannot establish real-system performance or hidden operating assumptions.
JAD-EV-16
Testing method, dataset, and verification-tool independence evidence record		verification-independencecurrentcurrentRe-review after verification-tool, model, dataset, oracle, reviewer, or test-design change.Different tools may still inherit one benchmark, oracle, assumption, or defect.

Verification ledger

Repeated testing is not independent verification

VerificationDimensionOriginalCurrentMethodIndependence requirement
JAD-VER-01
Independent check for software or model code lineage		code-lineagecurrentcurrentCompare declared artifacts, ownership, failure hypotheses, and observed behavior through a separate fictional evidence and review path.The method, dataset, tool, oracle, and reviewer chain must not simply reproduce the implementation being evaluated.
JAD-VER-02
Independent check for build pipeline and signing root		build-signingcurrentcurrentCompare declared artifacts, ownership, failure hypotheses, and observed behavior through a separate fictional evidence and review path.The method, dataset, tool, oracle, and reviewer chain must not simply reproduce the implementation being evaluated.
JAD-VER-03
Independent check for package repository and update channel		update-channelcurrentcurrentCompare declared artifacts, ownership, failure hypotheses, and observed behavior through a separate fictional evidence and review path.The method, dataset, tool, oracle, and reviewer chain must not simply reproduce the implementation being evaluated.
JAD-VER-04
Independent check for configuration-authoring authority		configuration-authoritycurrentcurrentCompare declared artifacts, ownership, failure hypotheses, and observed behavior through a separate fictional evidence and review path.The method, dataset, tool, oracle, and reviewer chain must not simply reproduce the implementation being evaluated.
JAD-VER-05
Independent check for identity provider and trust anchor		identity-trust-anchorcurrentcurrentCompare declared artifacts, ownership, failure hypotheses, and observed behavior through a separate fictional evidence and review path.The method, dataset, tool, oracle, and reviewer chain must not simply reproduce the implementation being evaluated.
JAD-VER-06
Independent check for trusted-time source and clock hardware		trusted-timecurrentcurrentCompare declared artifacts, ownership, failure hypotheses, and observed behavior through a separate fictional evidence and review path.The method, dataset, tool, oracle, and reviewer chain must not simply reproduce the implementation being evaluated.
JAD-VER-07
Independent check for power source and physical utility dependency		power-utilitycurrentcurrentCompare declared artifacts, ownership, failure hypotheses, and observed behavior through a separate fictional evidence and review path.The method, dataset, tool, oracle, and reviewer chain must not simply reproduce the implementation being evaluated.
JAD-VER-08
Independent check for communications gateway and carrier path		transport-carriercurrentcurrentCompare declared artifacts, ownership, failure hypotheses, and observed behavior through a separate fictional evidence and review path.The method, dataset, tool, oracle, and reviewer chain must not simply reproduce the implementation being evaluated.
JAD-VER-09
Independent check for semantic schema implementation and translator lineage		semantic-translatorcurrentcurrentCompare declared artifacts, ownership, failure hypotheses, and observed behavior through a separate fictional evidence and review path.The method, dataset, tool, oracle, and reviewer chain must not simply reproduce the implementation being evaluated.
JAD-VER-10
Independent check for data-product source and provenance chain		data-provenancecurrentcurrentCompare declared artifacts, ownership, failure hypotheses, and observed behavior through a separate fictional evidence and review path.The method, dataset, tool, oracle, and reviewer chain must not simply reproduce the implementation being evaluated.
JAD-VER-11
Independent check for compute architecture and regional hosting dependency		compute-hostingcurrentcurrentCompare declared artifacts, ownership, failure hypotheses, and observed behavior through a separate fictional evidence and review path.The method, dataset, tool, oracle, and reviewer chain must not simply reproduce the implementation being evaluated.
JAD-VER-12
Independent check for supplier, maintainer, and administrative ownership		supplier-administrationcurrentcurrentCompare declared artifacts, ownership, failure hypotheses, and observed behavior through a separate fictional evidence and review path.The method, dataset, tool, oracle, and reviewer chain must not simply reproduce the implementation being evaluated.
JAD-VER-13
Independent check for human-review pool and escalation chain		human-reviewcurrentcurrentCompare declared artifacts, ownership, failure hypotheses, and observed behavior through a separate fictional evidence and review path.The method, dataset, tool, oracle, and reviewer chain must not simply reproduce the implementation being evaluated.
JAD-VER-14
Independent check for assessment and reconciliation implementation		assessment-reconciliationcurrentcurrentCompare declared artifacts, ownership, failure hypotheses, and observed behavior through a separate fictional evidence and review path.The method, dataset, tool, oracle, and reviewer chain must not simply reproduce the implementation being evaluated.
JAD-VER-15
Independent check for operating-environment assumption		environment-assumptioncurrentcurrentCompare declared artifacts, ownership, failure hypotheses, and observed behavior through a separate fictional evidence and review path.The method, dataset, tool, oracle, and reviewer chain must not simply reproduce the implementation being evaluated.
JAD-VER-16
Independent check for testing method, dataset, and verification-tool independence		verification-independencecurrentcurrentCompare declared artifacts, ownership, failure hypotheses, and observed behavior through a separate fictional evidence and review path.The method, dataset, tool, oracle, and reviewer chain must not simply reproduce the implementation being evaluated.

Complete semantic graph

Cases, imported portfolio records, diversity 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 109 graph nodes
Node IDTypeLabelImported sourceOriginal stateCurrent state
JAD-CASE-01caseDisaster-response information routingJAP-CASE-01currentcurrent
JAP-CASE-01portfolio-caseImported portfolio case JAP-CASE-01—currentcurrent
JAP-DEP-01portfolio-dependencyShared identity and workload-trust service—currentcurrent
JAP-DEP-02portfolio-dependencyShared trusted-time and synchronization source—currentcurrent
JAP-DEP-03portfolio-dependencyShared semantic schema and translation gateway—currentcurrent
JAP-DEP-04portfolio-dependencyShared data-product provenance service—currentcurrent
JAP-DEP-05portfolio-dependencyShared software, model, and configuration lineage—currentcurrent
JAP-DEP-06portfolio-dependencyShared policy and permitted-purpose rule—currentcurrent
JAP-DEP-07portfolio-dependencyShared authority and delegation record—currentcurrent
JAP-DEP-08portfolio-dependencypartner-release—currentcurrent
JAP-DEP-09portfolio-dependencyShared communications and transport failure domain—currentcurrent
JAP-DEP-10portfolio-dependencyShared edge and regional compute capacity—currentcurrent
JAP-DEP-11portfolio-dependencyShared human-review role and workload pool—currentcurrent
JAP-DEP-12portfolio-dependencyShared assessment and reconciliation service—currentcurrent
JAP-DEP-13portfolio-dependencyShared update and rollback mechanism—currentcurrent
JAP-DEP-14portfolio-dependencyShared supply-chain and dependency family—currentcurrent
JAP-DEP-15portfolio-dependencyShared operating-environment assumption—currentcurrent
JAD-CASE-02caseInfrastructure-protection coordinationJAP-CASE-02currentcurrent
JAP-CASE-02portfolio-caseImported portfolio case JAP-CASE-02—currentcurrent
JAD-CASE-03caseMission-partner awareness and releasabilityJAP-CASE-03currentcurrent
JAP-CASE-03portfolio-caseImported portfolio case JAP-CASE-03—currentcurrent
JAD-CASE-04caseLogistics recovery after gateway lossJAP-CASE-04currentcurrent
JAP-CASE-04portfolio-caseImported portfolio case JAP-CASE-04—currentcurrent
JAD-CASE-05caseCyber-defense interpretation with contradictory evidenceJAP-CASE-05currentcurrent
JAP-CASE-05portfolio-caseImported portfolio case JAP-CASE-05—currentcurrent
JAD-CASE-06caseTime-critical protective supportJAP-CASE-06currentcurrent
JAP-CASE-06portfolio-caseImported portfolio case JAP-CASE-06—currentcurrent
JAD-DIM-01diversity-dimensionSoftware or model code lineage—currentcurrent
JAD-CLM-01diversity-claimDiversity claim: Software or model code lineage—currentcurrent
JAD-DIM-02diversity-dimensionBuild pipeline and signing root—currentcurrent
JAD-CLM-02diversity-claimDiversity claim: Build pipeline and signing root—currentcurrent
JAD-DIM-03diversity-dimensionPackage repository and update channel—currentcurrent
JAD-CLM-03diversity-claimDiversity claim: Package repository and update channel—currentcurrent
JAD-DIM-04diversity-dimensionConfiguration-authoring authority—currentcurrent
JAD-CLM-04diversity-claimDiversity claim: Configuration-authoring authority—currentcurrent
JAD-DIM-05diversity-dimensionIdentity provider and trust anchor—currentcurrent
JAD-CLM-05diversity-claimDiversity claim: Identity provider and trust anchor—currentcurrent
JAD-DIM-06diversity-dimensionTrusted-time source and clock hardware—currentcurrent
JAD-CLM-06diversity-claimDiversity claim: Trusted-time source and clock hardware—currentcurrent
JAD-DIM-07diversity-dimensionPower source and physical utility dependency—currentcurrent
JAD-CLM-07diversity-claimDiversity claim: Power source and physical utility dependency—currentcurrent
JAD-DIM-08diversity-dimensionCommunications gateway and carrier path—currentcurrent
JAD-CLM-08diversity-claimDiversity claim: Communications gateway and carrier path—currentcurrent
JAD-DIM-09diversity-dimensionSemantic schema implementation and translator lineage—currentcurrent
JAD-CLM-09diversity-claimDiversity claim: Semantic schema implementation and translator lineage—currentcurrent
JAD-DIM-10diversity-dimensionData-product source and provenance chain—currentcurrent
JAD-CLM-10diversity-claimDiversity claim: Data-product source and provenance chain—currentcurrent
JAD-DIM-11diversity-dimensionCompute architecture and regional hosting dependency—currentcurrent
JAD-CLM-11diversity-claimDiversity claim: Compute architecture and regional hosting dependency—currentcurrent
JAD-DIM-12diversity-dimensionSupplier, maintainer, and administrative ownership—currentcurrent
JAD-CLM-12diversity-claimDiversity claim: Supplier, maintainer, and administrative ownership—currentcurrent
JAD-DIM-13diversity-dimensionHuman-review pool and escalation chain—currentcurrent
JAD-CLM-13diversity-claimDiversity claim: Human-review pool and escalation chain—currentcurrent
JAD-DIM-14diversity-dimensionAssessment and reconciliation implementation—currentcurrent
JAD-CLM-14diversity-claimDiversity claim: Assessment and reconciliation implementation—currentcurrent
JAD-DIM-15diversity-dimensionOperating-environment assumption—currentcurrent
JAD-CLM-15diversity-claimDiversity claim: Operating-environment assumption—currentcurrent
JAD-DIM-16diversity-dimensionTesting method, dataset, and verification-tool independence—currentcurrent
JAD-CLM-16diversity-claimDiversity claim: Testing method, dataset, and verification-tool independence—currentcurrent
JAD-ROLE-01roleSoftware lineage custodian—currentcurrent
JAD-ROLE-02roleBuild and signing authority—currentcurrent
JAD-ROLE-03roleRepository and update-channel steward—currentcurrent
JAD-ROLE-04roleConfiguration-authoring authority—currentcurrent
JAD-ROLE-05roleIdentity and trust-anchor operator—currentcurrent
JAD-ROLE-06roleTrusted-time and clock steward—currentcurrent
JAD-ROLE-07rolePower and utility dependency steward—currentcurrent
JAD-ROLE-08roleTransport and gateway steward—currentcurrent
JAD-ROLE-09roleSemantic translator maintainer—currentcurrent
JAD-ROLE-10roleData-product and provenance steward—currentcurrent
JAD-ROLE-11roleCompute and hosting steward—currentcurrent
JAD-ROLE-12roleSupplier and maintenance administrator—currentcurrent
JAD-ROLE-13roleHuman merits-review pool owner—currentcurrent
JAD-ROLE-14roleAssessment and reconciliation owner—currentcurrent
JAD-ROLE-15roleOperating-environment assumption owner—currentcurrent
JAD-ROLE-16roleIndependent verification lead—currentcurrent
JAD-ROLE-17rolePortfolio assurance owner—currentcurrent
JAD-ROLE-18roleIndependent diversity and containment reviewer—currentcurrent
JAD-EV-01evidenceSoftware or model code lineage evidence record—currentcurrent
JAD-EV-02evidenceBuild pipeline and signing root evidence record—currentcurrent
JAD-EV-03evidencePackage repository and update channel evidence record—currentcurrent
JAD-EV-04evidenceConfiguration-authoring authority evidence record—currentcurrent
JAD-EV-05evidenceIdentity provider and trust anchor evidence record—currentcurrent
JAD-EV-06evidenceTrusted-time source and clock hardware evidence record—currentcurrent
JAD-EV-07evidencePower source and physical utility dependency evidence record—currentcurrent
JAD-EV-08evidenceCommunications gateway and carrier path evidence record—currentcurrent
JAD-EV-09evidenceSemantic schema implementation and translator lineage evidence record—currentcurrent
JAD-EV-10evidenceData-product source and provenance chain evidence record—currentcurrent
JAD-EV-11evidenceCompute architecture and regional hosting dependency evidence record—currentcurrent
JAD-EV-12evidenceSupplier, maintainer, and administrative ownership evidence record—currentcurrent
JAD-EV-13evidenceHuman-review pool and escalation chain evidence record—currentcurrent
JAD-EV-14evidenceAssessment and reconciliation implementation evidence record—currentcurrent
JAD-EV-15evidenceOperating-environment assumption evidence record—currentcurrent
JAD-EV-16evidenceTesting method, dataset, and verification-tool independence evidence record—currentcurrent
JAD-VER-01verificationIndependent check for software or model code lineage—currentcurrent
JAD-VER-02verificationIndependent check for build pipeline and signing root—currentcurrent
JAD-VER-03verificationIndependent check for package repository and update channel—currentcurrent
JAD-VER-04verificationIndependent check for configuration-authoring authority—currentcurrent
JAD-VER-05verificationIndependent check for identity provider and trust anchor—currentcurrent
JAD-VER-06verificationIndependent check for trusted-time source and clock hardware—currentcurrent
JAD-VER-07verificationIndependent check for power source and physical utility dependency—currentcurrent
JAD-VER-08verificationIndependent check for communications gateway and carrier path—currentcurrent
JAD-VER-09verificationIndependent check for semantic schema implementation and translator lineage—currentcurrent
JAD-VER-10verificationIndependent check for data-product source and provenance chain—currentcurrent
JAD-VER-11verificationIndependent check for compute architecture and regional hosting dependency—currentcurrent
JAD-VER-12verificationIndependent check for supplier, maintainer, and administrative ownership—currentcurrent
JAD-VER-13verificationIndependent check for human-review pool and escalation chain—currentcurrent
JAD-VER-14verificationIndependent check for assessment and reconciliation implementation—currentcurrent
JAD-VER-15verificationIndependent check for operating-environment assumption—currentcurrent
JAD-VER-16verificationIndependent check for testing method, dataset, and verification-tool independence—currentcurrent
Inspect all 225 graph relationships
FromRelationshipToOriginal stateCurrent state
JAD-CASE-01imports-stable-caseJAP-CASE-01currentcurrent
JAD-CASE-01depends-onJAP-DEP-01currentcurrent
JAD-CASE-01depends-onJAP-DEP-02currentcurrent
JAD-CASE-01depends-onJAP-DEP-03currentcurrent
JAD-CASE-01depends-onJAP-DEP-04currentcurrent
JAD-CASE-01depends-onJAP-DEP-05currentcurrent
JAD-CASE-01depends-onJAP-DEP-06currentcurrent
JAD-CASE-01depends-onJAP-DEP-07currentcurrent
JAD-CASE-01depends-onJAP-DEP-08currentcurrent
JAD-CASE-01depends-onJAP-DEP-09currentcurrent
JAD-CASE-01depends-onJAP-DEP-10currentcurrent
JAD-CASE-01depends-onJAP-DEP-11currentcurrent
JAD-CASE-01depends-onJAP-DEP-12currentcurrent
JAD-CASE-01depends-onJAP-DEP-13currentcurrent
JAD-CASE-01depends-onJAP-DEP-14currentcurrent
JAD-CASE-01depends-onJAP-DEP-15currentcurrent
JAD-CASE-02imports-stable-caseJAP-CASE-02currentcurrent
JAD-CASE-02depends-onJAP-DEP-01currentcurrent
JAD-CASE-02depends-onJAP-DEP-02currentcurrent
JAD-CASE-02depends-onJAP-DEP-03currentcurrent
JAD-CASE-02depends-onJAP-DEP-04currentcurrent
JAD-CASE-02depends-onJAP-DEP-05currentcurrent
JAD-CASE-02depends-onJAP-DEP-06currentcurrent
JAD-CASE-02depends-onJAP-DEP-07currentcurrent
JAD-CASE-02depends-onJAP-DEP-09currentcurrent
JAD-CASE-02depends-onJAP-DEP-10currentcurrent
JAD-CASE-02depends-onJAP-DEP-11currentcurrent
JAD-CASE-02depends-onJAP-DEP-12currentcurrent
JAD-CASE-02depends-onJAP-DEP-13currentcurrent
JAD-CASE-02depends-onJAP-DEP-14currentcurrent
JAD-CASE-02depends-onJAP-DEP-15currentcurrent
JAD-CASE-03imports-stable-caseJAP-CASE-03currentcurrent
JAD-CASE-03depends-onJAP-DEP-01currentcurrent
JAD-CASE-03depends-onJAP-DEP-02currentcurrent
JAD-CASE-03depends-onJAP-DEP-03currentcurrent
JAD-CASE-03depends-onJAP-DEP-04currentcurrent
JAD-CASE-03depends-onJAP-DEP-05currentcurrent
JAD-CASE-03depends-onJAP-DEP-06currentcurrent
JAD-CASE-03depends-onJAP-DEP-07currentcurrent
JAD-CASE-03depends-onJAP-DEP-08currentcurrent
JAD-CASE-03depends-onJAP-DEP-09currentcurrent
JAD-CASE-03depends-onJAP-DEP-10currentcurrent
JAD-CASE-03depends-onJAP-DEP-11currentcurrent
JAD-CASE-03depends-onJAP-DEP-12currentcurrent
JAD-CASE-03depends-onJAP-DEP-13currentcurrent
JAD-CASE-03depends-onJAP-DEP-14currentcurrent
JAD-CASE-03depends-onJAP-DEP-15currentcurrent
JAD-CASE-04imports-stable-caseJAP-CASE-04currentcurrent
JAD-CASE-04depends-onJAP-DEP-01currentcurrent
JAD-CASE-04depends-onJAP-DEP-02currentcurrent
JAD-CASE-04depends-onJAP-DEP-03currentcurrent
JAD-CASE-04depends-onJAP-DEP-04currentcurrent
JAD-CASE-04depends-onJAP-DEP-05currentcurrent
JAD-CASE-04depends-onJAP-DEP-06currentcurrent
JAD-CASE-04depends-onJAP-DEP-07currentcurrent
JAD-CASE-04depends-onJAP-DEP-09currentcurrent
JAD-CASE-04depends-onJAP-DEP-10currentcurrent
JAD-CASE-04depends-onJAP-DEP-11currentcurrent
JAD-CASE-04depends-onJAP-DEP-12currentcurrent
JAD-CASE-04depends-onJAP-DEP-13currentcurrent
JAD-CASE-04depends-onJAP-DEP-14currentcurrent
JAD-CASE-04depends-onJAP-DEP-15currentcurrent
JAD-CASE-05imports-stable-caseJAP-CASE-05currentcurrent
JAD-CASE-05depends-onJAP-DEP-01currentcurrent
JAD-CASE-05depends-onJAP-DEP-02currentcurrent
JAD-CASE-05depends-onJAP-DEP-03currentcurrent
JAD-CASE-05depends-onJAP-DEP-04currentcurrent
JAD-CASE-05depends-onJAP-DEP-05currentcurrent
JAD-CASE-05depends-onJAP-DEP-06currentcurrent
JAD-CASE-05depends-onJAP-DEP-07currentcurrent
JAD-CASE-05depends-onJAP-DEP-10currentcurrent
JAD-CASE-05depends-onJAP-DEP-11currentcurrent
JAD-CASE-05depends-onJAP-DEP-12currentcurrent
JAD-CASE-05depends-onJAP-DEP-13currentcurrent
JAD-CASE-05depends-onJAP-DEP-14currentcurrent
JAD-CASE-05depends-onJAP-DEP-15currentcurrent
JAD-CASE-06imports-stable-caseJAP-CASE-06currentcurrent
JAD-CASE-06depends-onJAP-DEP-01currentcurrent
JAD-CASE-06depends-onJAP-DEP-02currentcurrent
JAD-CASE-06depends-onJAP-DEP-03currentcurrent
JAD-CASE-06depends-onJAP-DEP-04currentcurrent
JAD-CASE-06depends-onJAP-DEP-05currentcurrent
JAD-CASE-06depends-onJAP-DEP-06currentcurrent
JAD-CASE-06depends-onJAP-DEP-07currentcurrent
JAD-CASE-06depends-onJAP-DEP-08currentcurrent
JAD-CASE-06depends-onJAP-DEP-09currentcurrent
JAD-CASE-06depends-onJAP-DEP-10currentcurrent
JAD-CASE-06depends-onJAP-DEP-11currentcurrent
JAD-CASE-06depends-onJAP-DEP-12currentcurrent
JAD-CASE-06depends-onJAP-DEP-13currentcurrent
JAD-CASE-06depends-onJAP-DEP-14currentcurrent
JAD-CASE-06depends-onJAP-DEP-15currentcurrent
JAD-CLM-01evaluatesJAD-DIM-01currentcurrent
JAD-DIM-01tests-independence-ofJAP-DEP-05currentcurrent
JAD-DIM-01tests-independence-ofJAP-DEP-14currentcurrent
JAD-CLM-01requires-role-evidenceJAD-ROLE-01currentcurrent
JAD-CLM-01requires-role-evidenceJAD-ROLE-12currentcurrent
JAD-CLM-01requires-role-evidenceJAD-ROLE-16currentcurrent
JAD-CLM-01requires-role-evidenceJAD-ROLE-18currentreview-required
JAD-CLM-01supported-byJAD-EV-01currentcurrent
JAD-CLM-01verified-byJAD-VER-01currentcurrent
JAD-CLM-02evaluatesJAD-DIM-02currentcurrent
JAD-DIM-02tests-independence-ofJAP-DEP-05currentcurrent
JAD-DIM-02tests-independence-ofJAP-DEP-13currentcurrent
JAD-DIM-02tests-independence-ofJAP-DEP-14currentcurrent
JAD-CLM-02requires-role-evidenceJAD-ROLE-02currentcurrent
JAD-CLM-02requires-role-evidenceJAD-ROLE-03currentcurrent
JAD-CLM-02requires-role-evidenceJAD-ROLE-16currentcurrent
JAD-CLM-02requires-role-evidenceJAD-ROLE-18currentreview-required
JAD-CLM-02supported-byJAD-EV-02currentcurrent
JAD-CLM-02verified-byJAD-VER-02currentcurrent
JAD-CLM-03evaluatesJAD-DIM-03currentcurrent
JAD-DIM-03tests-independence-ofJAP-DEP-13currentcurrent
JAD-DIM-03tests-independence-ofJAP-DEP-14currentcurrent
JAD-CLM-03requires-role-evidenceJAD-ROLE-03currentcurrent
JAD-CLM-03requires-role-evidenceJAD-ROLE-12currentcurrent
JAD-CLM-03requires-role-evidenceJAD-ROLE-16currentcurrent
JAD-CLM-03requires-role-evidenceJAD-ROLE-18currentreview-required
JAD-CLM-03supported-byJAD-EV-03currentcurrent
JAD-CLM-03verified-byJAD-VER-03currentcurrent
JAD-CLM-04evaluatesJAD-DIM-04currentcurrent
JAD-DIM-04tests-independence-ofJAP-DEP-05currentcurrent
JAD-DIM-04tests-independence-ofJAP-DEP-06currentcurrent
JAD-DIM-04tests-independence-ofJAP-DEP-07currentcurrent
JAD-CLM-04requires-role-evidenceJAD-ROLE-04currentcurrent
JAD-CLM-04requires-role-evidenceJAD-ROLE-17currentreview-required
JAD-CLM-04requires-role-evidenceJAD-ROLE-18currentreview-required
JAD-CLM-04supported-byJAD-EV-04currentcurrent
JAD-CLM-04verified-byJAD-VER-04currentcurrent
JAD-CLM-05evaluatesJAD-DIM-05currentcurrent
JAD-DIM-05tests-independence-ofJAP-DEP-01currentcurrent
JAD-CLM-05requires-role-evidenceJAD-ROLE-05currentcurrent
JAD-CLM-05requires-role-evidenceJAD-ROLE-16currentcurrent
JAD-CLM-05requires-role-evidenceJAD-ROLE-18currentreview-required
JAD-CLM-05supported-byJAD-EV-05currentcurrent
JAD-CLM-05verified-byJAD-VER-05currentcurrent
JAD-CLM-06evaluatesJAD-DIM-06currentcurrent
JAD-DIM-06tests-independence-ofJAP-DEP-02currentcurrent
JAD-CLM-06requires-role-evidenceJAD-ROLE-06currentcurrent
JAD-CLM-06requires-role-evidenceJAD-ROLE-16currentcurrent
JAD-CLM-06requires-role-evidenceJAD-ROLE-18currentreview-required
JAD-CLM-06supported-byJAD-EV-06currentcurrent
JAD-CLM-06verified-byJAD-VER-06currentcurrent
JAD-CLM-07evaluatesJAD-DIM-07currentcurrent
JAD-DIM-07tests-independence-ofJAP-DEP-10currentcurrent
JAD-DIM-07tests-independence-ofJAP-DEP-09currentcurrent
JAD-DIM-07tests-independence-ofJAP-DEP-15currentcurrent
JAD-CLM-07requires-role-evidenceJAD-ROLE-07currentcurrent
JAD-CLM-07requires-role-evidenceJAD-ROLE-11currentcurrent
JAD-CLM-07requires-role-evidenceJAD-ROLE-18currentreview-required
JAD-CLM-07supported-byJAD-EV-07currentcurrent
JAD-CLM-07verified-byJAD-VER-07currentcurrent
JAD-CLM-08evaluatesJAD-DIM-08currentcurrent
JAD-DIM-08tests-independence-ofJAP-DEP-09currentcurrent
JAD-CLM-08requires-role-evidenceJAD-ROLE-08currentcurrent
JAD-CLM-08requires-role-evidenceJAD-ROLE-16currentcurrent
JAD-CLM-08requires-role-evidenceJAD-ROLE-18currentreview-required
JAD-CLM-08supported-byJAD-EV-08currentcurrent
JAD-CLM-08verified-byJAD-VER-08currentcurrent
JAD-CLM-09evaluatesJAD-DIM-09currentcurrent
JAD-DIM-09tests-independence-ofJAP-DEP-03currentcurrent
JAD-DIM-09tests-independence-ofJAP-DEP-05currentcurrent
JAD-DIM-09tests-independence-ofJAP-DEP-14currentcurrent
JAD-CLM-09requires-role-evidenceJAD-ROLE-09currentcurrent
JAD-CLM-09requires-role-evidenceJAD-ROLE-16currentcurrent
JAD-CLM-09requires-role-evidenceJAD-ROLE-18currentreview-required
JAD-CLM-09supported-byJAD-EV-09currentcurrent
JAD-CLM-09verified-byJAD-VER-09currentcurrent
JAD-CLM-10evaluatesJAD-DIM-10currentcurrent
JAD-DIM-10tests-independence-ofJAP-DEP-04currentcurrent
JAD-CLM-10requires-role-evidenceJAD-ROLE-10currentcurrent
JAD-CLM-10requires-role-evidenceJAD-ROLE-16currentcurrent
JAD-CLM-10requires-role-evidenceJAD-ROLE-18currentreview-required
JAD-CLM-10supported-byJAD-EV-10currentcurrent
JAD-CLM-10verified-byJAD-VER-10currentcurrent
JAD-CLM-11evaluatesJAD-DIM-11currentcurrent
JAD-DIM-11tests-independence-ofJAP-DEP-10currentcurrent
JAD-DIM-11tests-independence-ofJAP-DEP-05currentcurrent
JAD-DIM-11tests-independence-ofJAP-DEP-15currentcurrent
JAD-CLM-11requires-role-evidenceJAD-ROLE-11currentcurrent
JAD-CLM-11requires-role-evidenceJAD-ROLE-12currentcurrent
JAD-CLM-11requires-role-evidenceJAD-ROLE-18currentreview-required
JAD-CLM-11supported-byJAD-EV-11currentcurrent
JAD-CLM-11verified-byJAD-VER-11currentcurrent
JAD-CLM-12evaluatesJAD-DIM-12currentcurrent
JAD-DIM-12tests-independence-ofJAP-DEP-14currentcurrent
JAD-DIM-12tests-independence-ofJAP-DEP-05currentcurrent
JAD-DIM-12tests-independence-ofJAP-DEP-01currentcurrent
JAD-CLM-12requires-role-evidenceJAD-ROLE-12currentcurrent
JAD-CLM-12requires-role-evidenceJAD-ROLE-05currentcurrent
JAD-CLM-12requires-role-evidenceJAD-ROLE-18currentreview-required
JAD-CLM-12supported-byJAD-EV-12currentcurrent
JAD-CLM-12verified-byJAD-VER-12currentcurrent
JAD-CLM-13evaluatesJAD-DIM-13currentcurrent
JAD-DIM-13tests-independence-ofJAP-DEP-11currentcurrent
JAD-DIM-13tests-independence-ofJAP-DEP-07currentcurrent
JAD-CLM-13requires-role-evidenceJAD-ROLE-13currentcurrent
JAD-CLM-13requires-role-evidenceJAD-ROLE-17currentreview-required
JAD-CLM-13requires-role-evidenceJAD-ROLE-18currentreview-required
JAD-CLM-13supported-byJAD-EV-13currentcurrent
JAD-CLM-13verified-byJAD-VER-13currentcurrent
JAD-CLM-14evaluatesJAD-DIM-14currentcurrent
JAD-DIM-14tests-independence-ofJAP-DEP-12currentcurrent
JAD-DIM-14tests-independence-ofJAP-DEP-05currentcurrent
JAD-CLM-14requires-role-evidenceJAD-ROLE-14currentcurrent
JAD-CLM-14requires-role-evidenceJAD-ROLE-16currentcurrent
JAD-CLM-14requires-role-evidenceJAD-ROLE-18currentreview-required
JAD-CLM-14supported-byJAD-EV-14currentcurrent
JAD-CLM-14verified-byJAD-VER-14currentcurrent
JAD-CLM-15evaluatesJAD-DIM-15currentcurrent
JAD-DIM-15tests-independence-ofJAP-DEP-15currentcurrent
JAD-CLM-15requires-role-evidenceJAD-ROLE-15currentcurrent
JAD-CLM-15requires-role-evidenceJAD-ROLE-16currentcurrent
JAD-CLM-15requires-role-evidenceJAD-ROLE-18currentreview-required
JAD-CLM-15supported-byJAD-EV-15currentcurrent
JAD-CLM-15verified-byJAD-VER-15currentcurrent
JAD-CLM-16evaluatesJAD-DIM-16currentcurrent
JAD-DIM-16tests-independence-ofJAP-DEP-05currentcurrent
JAD-DIM-16tests-independence-ofJAP-DEP-14currentcurrent
JAD-DIM-16tests-independence-ofJAP-DEP-11currentcurrent
JAD-CLM-16requires-role-evidenceJAD-ROLE-16currentcurrent
JAD-CLM-16requires-role-evidenceJAD-ROLE-17currentreview-required
JAD-CLM-16requires-role-evidenceJAD-ROLE-18currentreview-required
JAD-CLM-16supported-byJAD-EV-16currentcurrent
JAD-CLM-16verified-byJAD-VER-16currentcurrent

Affected evidence

  • No evidence record is changed in the selected baseline state.

Verification to repeat

  • No additional verification is required in the selected baseline state.

Direct answers

What diversity evidence can and cannot establish

What is the difference between redundancy, diversity, and independence?

Redundancy means another instance, path, or capacity exists. Diversity means the alternative differs materially in a declared implementation or evidence dimension. Independence means the alternatives do not share the relevant failure cause for the stated scope. None of those conditions alone creates authority or certification.

Do different products or vendors prove implementation diversity?

No. Different names or vendors may still share source code, libraries, builders, signing roots, repositories, administrators, suppliers, schemas, data sources, or verification tools. The claim must be tied to current artifacts and a declared failure hypothesis.

Why can different regions still fail together?

Separate regions may depend on one identity provider, physical time reference, power grid, carrier, control plane, repository, administrator, facility utility, or common image. Geography alone does not establish an independent failure domain.

What makes verification genuinely independent?

Independent verification uses a meaningfully different method, dataset, tool, oracle, reviewer chain, and failure hypothesis. Repeating the same test with another process or interface can reproduce the same blind spot.

Does a complete diversity graph certify a JADC2 portfolio?

No. The graph makes declared claims, evidence, common dependencies, expiry, verification, containment, and residual unknowns visible. It cannot prove that a real system has no hidden common cause, nor can it determine readiness, legality, command authority, safety, certification, or deployment approval.

Can this lab accept real software, SBOMs, certificates, logs, or architecture details?

No. It accepts only one allowlisted fictional change. It performs no upload, external request, evidence transfer, real-system assessment, classified-dependency inference, Evulgare integration, or operational portfolio optimization.

Public synthetic boundary

The output is a diversity-evidence and review posture—not a real-system assessment.

The lab cannot accept or infer a real architecture, classified dependency, software artifact, model, SBOM, certificate, key, supplier, organization, system, target, route, mission, evidence package, or authority instrument. It cannot 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 diversity graph makes declared relationships visible; it does not prove universal independence or the absence of hidden common causes.

Continue the JADC2 pathway

Move from enterprise meaning to convergence, replay, case assurance, common modes, and diversity evidence.

Each module answers a different question and preserves a different truth boundary.

JADC2 Overview Mission-Thread Convergence Evidence Replay Change Impact & Assurance Assurance Portfolio Evulgare real-system evidence