[
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/artificial-intelligence-vs-machine-intelligence/#clm-k03-cmp-001",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K03 RECORD",
    "id": "CLM-K03-CMP-001",
    "lastReviewed": "2026-08-14",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-001.json",
    "name": "Artificial Intelligence versus Machine Intelligence",
    "ownerAnchor": "clm-k03-cmp-001",
    "ownerId": "K01-CMP-001",
    "ownerRoute": "/comparisons/artificial-intelligence-vs-machine-intelligence/",
    "ownerType": "comparison",
    "proposition": "Artificial Intelligence is a broad field and regulatory category; Machine Intelligence is a project term for an instantiated actor evaluated through identity, continuity, agency and evidence.",
    "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-14",
    "scope": "Canonical distinction between Artificial Intelligence and Machine Intelligence.",
    "slug": "clm-k03-cmp-001",
    "sourceIds": [
      "SRC-NIST-AI-RMF",
      "SRC-W3C-PROV-O",
      "SRC-EU-AI-ACT"
    ],
    "sourceSections": [
      {
        "section": "AI RMF 1.0 publication",
        "sourceId": "SRC-NIST-AI-RMF",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "NIST AI RMF 1.0 is a voluntary risk-management framework with Govern, Map, Measure, and Manage functions.",
        "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf"
      },
      {
        "section": "Current revision notice",
        "sourceId": "SRC-NIST-AI-RMF",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "NIST states that AI RMF 1.0 is being revised.",
        "url": "https://www.nist.gov/artificial-intelligence/ai-standards"
      },
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "PROV-O at a glance",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.",
        "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance"
      },
      {
        "section": "Application timeline",
        "sourceId": "SRC-EU-AI-ACT",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.",
        "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline"
      },
      {
        "section": "AI Omnibus simplification timeline",
        "sourceId": "SRC-EU-AI-ACT",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.",
        "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act"
      },
      {
        "section": "Governance and enforcement",
        "sourceId": "SRC-EU-AI-ACT",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.",
        "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/identity-vs-credential/#clm-k03-cmp-002",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K03 RECORD",
    "id": "CLM-K03-CMP-002",
    "lastReviewed": "2026-08-14",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-002.json",
    "name": "Identity versus Credential",
    "ownerAnchor": "clm-k03-cmp-002",
    "ownerId": "K01-CMP-002",
    "ownerRoute": "/comparisons/identity-vs-credential/",
    "ownerType": "comparison",
    "proposition": "Identity is the subject-continuity claim; a credential is an issued representation of one or more claims about that subject.",
    "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-14",
    "scope": "Canonical distinction between Identity and Credential.",
    "slug": "clm-k03-cmp-002",
    "sourceIds": [
      "SRC-W3C-DID-CORE",
      "SRC-W3C-VC-DM",
      "SRC-RFC-5280",
      "SRC-W3C-PROV-O"
    ],
    "sourceSections": [
      {
        "section": "Verification methods",
        "sourceId": "SRC-W3C-DID-CORE",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "A DID document can express verification methods associated with a DID subject.",
        "url": "https://www.w3.org/TR/did-core/#verification-methods"
      },
      {
        "section": "Services",
        "sourceId": "SRC-W3C-DID-CORE",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "A DID document can advertise service endpoints; that does not itself establish legal identity or authority.",
        "url": "https://www.w3.org/TR/did-core/#services"
      },
      {
        "section": "Abstract",
        "sourceId": "SRC-W3C-VC-DM",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.",
        "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract"
      },
      {
        "section": "Ecosystem overview",
        "sourceId": "SRC-W3C-VC-DM",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.",
        "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview"
      },
      {
        "section": "RFC status and update chain",
        "sourceId": "SRC-RFC-5280",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "RFC 5280 is a Proposed Standard and has been updated by later RFCs.",
        "url": "https://www.rfc-editor.org/info/rfc5280/"
      },
      {
        "section": "Certificate and CRL profile",
        "sourceId": "SRC-RFC-5280",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The RFC profiles X.509 certificates and revocation lists; a valid certificate binds data under a PKI but does not establish every external legal or factual claim.",
        "url": "https://www.rfc-editor.org/rfc/rfc5280.html#section-4"
      },
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "PROV-O at a glance",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.",
        "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/evidence-vs-truth/#clm-k03-cmp-003",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K03 RECORD",
    "id": "CLM-K03-CMP-003",
    "lastReviewed": "2026-08-14",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-003.json",
    "name": "Evidence versus Truth",
    "ownerAnchor": "clm-k03-cmp-003",
    "ownerId": "K01-CMP-003",
    "ownerRoute": "/comparisons/evidence-vs-truth/",
    "ownerType": "comparison",
    "proposition": "Evidence supports or challenges a proposition; truth concerns whether the proposition corresponds to reality.",
    "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-14",
    "scope": "Canonical distinction between Evidence and Truth.",
    "slug": "clm-k03-cmp-003",
    "sourceIds": [
      "SRC-W3C-PROV-O",
      "SRC-RFC-3161",
      "SRC-C2PA",
      "SRC-IN-TOTO"
    ],
    "sourceSections": [
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "PROV-O at a glance",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.",
        "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance"
      },
      {
        "section": "RFC status and update chain",
        "sourceId": "SRC-RFC-3161",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.",
        "url": "https://www.rfc-editor.org/info/rfc3161/"
      },
      {
        "section": "Overview",
        "sourceId": "SRC-RFC-3161",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.",
        "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1"
      },
      {
        "section": "Version history — 2.4",
        "sourceId": "SRC-C2PA",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.",
        "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026"
      },
      {
        "section": "Core provenance principle",
        "sourceId": "SRC-C2PA",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.",
        "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles"
      },
      {
        "section": "Project overview",
        "sourceId": "SRC-IN-TOTO",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.",
        "url": "https://in-toto.io/"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/authentication-vs-authority/#clm-k03-cmp-004",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K03 RECORD",
    "id": "CLM-K03-CMP-004",
    "lastReviewed": "2026-08-14",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-004.json",
    "name": "Authentication versus Authority",
    "ownerAnchor": "clm-k03-cmp-004",
    "ownerId": "K01-CMP-004",
    "ownerRoute": "/comparisons/authentication-vs-authority/",
    "ownerType": "comparison",
    "proposition": "Authentication checks identity or credential control; authority defines the recognized power to make a particular decision or action.",
    "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-14",
    "scope": "Canonical distinction between Authentication and Authority.",
    "slug": "clm-k03-cmp-004",
    "sourceIds": [
      "SRC-W3C-DID-CORE",
      "SRC-W3C-VC-DM",
      "SRC-RFC-5280",
      "SRC-W3C-PROV-O"
    ],
    "sourceSections": [
      {
        "section": "Verification methods",
        "sourceId": "SRC-W3C-DID-CORE",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "A DID document can express verification methods associated with a DID subject.",
        "url": "https://www.w3.org/TR/did-core/#verification-methods"
      },
      {
        "section": "Services",
        "sourceId": "SRC-W3C-DID-CORE",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "A DID document can advertise service endpoints; that does not itself establish legal identity or authority.",
        "url": "https://www.w3.org/TR/did-core/#services"
      },
      {
        "section": "Abstract",
        "sourceId": "SRC-W3C-VC-DM",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.",
        "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract"
      },
      {
        "section": "Ecosystem overview",
        "sourceId": "SRC-W3C-VC-DM",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.",
        "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview"
      },
      {
        "section": "RFC status and update chain",
        "sourceId": "SRC-RFC-5280",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "RFC 5280 is a Proposed Standard and has been updated by later RFCs.",
        "url": "https://www.rfc-editor.org/info/rfc5280/"
      },
      {
        "section": "Certificate and CRL profile",
        "sourceId": "SRC-RFC-5280",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The RFC profiles X.509 certificates and revocation lists; a valid certificate binds data under a PKI but does not establish every external legal or factual claim.",
        "url": "https://www.rfc-editor.org/rfc/rfc5280.html#section-4"
      },
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "PROV-O at a glance",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.",
        "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/agency-vs-autonomy/#clm-k03-cmp-005",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K03 RECORD",
    "id": "CLM-K03-CMP-005",
    "lastReviewed": "2026-08-14",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-005.json",
    "name": "Agency versus Autonomy",
    "ownerAnchor": "clm-k03-cmp-005",
    "ownerId": "K01-CMP-005",
    "ownerRoute": "/comparisons/agency-vs-autonomy/",
    "ownerType": "comparison",
    "proposition": "Agency concerns attributable action selection; autonomy concerns independence from immediate external direction.",
    "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-14",
    "scope": "Canonical distinction between Agency and Autonomy.",
    "slug": "clm-k03-cmp-005",
    "sourceIds": [
      "SRC-NIST-AI-RMF",
      "SRC-W3C-PROV-O"
    ],
    "sourceSections": [
      {
        "section": "AI RMF 1.0 publication",
        "sourceId": "SRC-NIST-AI-RMF",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "NIST AI RMF 1.0 is a voluntary risk-management framework with Govern, Map, Measure, and Manage functions.",
        "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf"
      },
      {
        "section": "Current revision notice",
        "sourceId": "SRC-NIST-AI-RMF",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "NIST states that AI RMF 1.0 is being revised.",
        "url": "https://www.nist.gov/artificial-intelligence/ai-standards"
      },
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "PROV-O at a glance",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.",
        "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/autonomy-vs-sovereignty/#clm-k03-cmp-006",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K03 RECORD",
    "id": "CLM-K03-CMP-006",
    "lastReviewed": "2026-08-14",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-006.json",
    "name": "Autonomy versus Sovereignty",
    "ownerAnchor": "clm-k03-cmp-006",
    "ownerId": "K01-CMP-006",
    "ownerRoute": "/comparisons/autonomy-vs-sovereignty/",
    "ownerType": "comparison",
    "proposition": "Autonomy is operational independence within constraints; sovereignty is ultimate public authority within a jurisdictional order.",
    "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-14",
    "scope": "Canonical distinction between Autonomy and Sovereignty.",
    "slug": "clm-k03-cmp-006",
    "sourceIds": [
      "SRC-EU-AI-ACT",
      "SRC-OECD-AI-PRINCIPLES"
    ],
    "sourceSections": [
      {
        "section": "Application timeline",
        "sourceId": "SRC-EU-AI-ACT",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.",
        "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline"
      },
      {
        "section": "AI Omnibus simplification timeline",
        "sourceId": "SRC-EU-AI-ACT",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.",
        "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act"
      },
      {
        "section": "Governance and enforcement",
        "sourceId": "SRC-EU-AI-ACT",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.",
        "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement"
      },
      {
        "section": "Principles overview",
        "sourceId": "SRC-OECD-AI-PRINCIPLES",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The principles promote innovative and trustworthy AI consistent with human rights and democratic values and guide policy development.",
        "url": "https://oecd.ai/en/ai-principles"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/memory-continuity-vs-consciousness/#clm-k03-cmp-007",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K03 RECORD",
    "id": "CLM-K03-CMP-007",
    "lastReviewed": "2026-08-14",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-007.json",
    "name": "Memory Continuity versus Consciousness",
    "ownerAnchor": "clm-k03-cmp-007",
    "ownerId": "K01-CMP-007",
    "ownerRoute": "/comparisons/memory-continuity-vs-consciousness/",
    "ownerType": "comparison",
    "proposition": "Memory continuity concerns persistent influence of prior state; consciousness concerns subjective experience or awareness under a stated theory.",
    "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-14",
    "scope": "Canonical distinction between Memory Continuity and Consciousness.",
    "slug": "clm-k03-cmp-007",
    "sourceIds": [
      "SRC-W3C-PROV-O",
      "SRC-SLSA",
      "SRC-IN-TOTO"
    ],
    "sourceSections": [
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "PROV-O at a glance",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.",
        "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance"
      },
      {
        "section": "Specification status",
        "sourceId": "SRC-SLSA",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "SLSA v1.2 is an approved specification for incrementally improving software supply-chain security.",
        "url": "https://slsa.dev/spec/v1.2/"
      },
      {
        "section": "Build requirements",
        "sourceId": "SRC-SLSA",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "SLSA levels and provenance requirements qualify build evidence; they do not prove that a deployed service is currently operating.",
        "url": "https://slsa.dev/spec/v1.2/build-requirements"
      },
      {
        "section": "Project overview",
        "sourceId": "SRC-IN-TOTO",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.",
        "url": "https://in-toto.io/"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/technical-control-vs-legal-ownership/#clm-k03-cmp-008",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K03 RECORD",
    "id": "CLM-K03-CMP-008",
    "lastReviewed": "2026-08-14",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-008.json",
    "name": "Technical Control versus Legal Ownership",
    "ownerAnchor": "clm-k03-cmp-008",
    "ownerId": "K01-CMP-008",
    "ownerRoute": "/comparisons/technical-control-vs-legal-ownership/",
    "ownerType": "comparison",
    "proposition": "Technical control is the practical ability to access or direct a resource; legal ownership is a recognized title carrying enforceable rights and duties.",
    "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-14",
    "scope": "Canonical distinction between Technical Control and Legal Ownership.",
    "slug": "clm-k03-cmp-008",
    "sourceIds": [
      "SRC-W3C-VC-DM",
      "SRC-NIST-800-53"
    ],
    "sourceSections": [
      {
        "section": "Abstract",
        "sourceId": "SRC-W3C-VC-DM",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.",
        "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract"
      },
      {
        "section": "Ecosystem overview",
        "sourceId": "SRC-W3C-VC-DM",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.",
        "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview"
      },
      {
        "section": "Planning note — Release 5.2.0",
        "sourceId": "SRC-NIST-800-53",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.",
        "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final"
      },
      {
        "section": "Publication purpose",
        "sourceId": "SRC-NIST-800-53",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.",
        "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/registry-vs-governance/#clm-k03-cmp-009",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K03 RECORD",
    "id": "CLM-K03-CMP-009",
    "lastReviewed": "2026-08-14",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-009.json",
    "name": "Registry versus Governance",
    "ownerAnchor": "clm-k03-cmp-009",
    "ownerId": "K01-CMP-009",
    "ownerRoute": "/comparisons/registry-vs-governance/",
    "ownerType": "comparison",
    "proposition": "A registry records statuses under rules; governance creates, interprets and oversees the legitimate rules and authorities.",
    "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-14",
    "scope": "Canonical distinction between Registry and Governance.",
    "slug": "clm-k03-cmp-009",
    "sourceIds": [
      "SRC-W3C-VC-DM",
      "SRC-W3C-DID-CORE",
      "SRC-W3C-PROV-O"
    ],
    "sourceSections": [
      {
        "section": "Abstract",
        "sourceId": "SRC-W3C-VC-DM",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.",
        "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract"
      },
      {
        "section": "Ecosystem overview",
        "sourceId": "SRC-W3C-VC-DM",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.",
        "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview"
      },
      {
        "section": "Verification methods",
        "sourceId": "SRC-W3C-DID-CORE",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "A DID document can express verification methods associated with a DID subject.",
        "url": "https://www.w3.org/TR/did-core/#verification-methods"
      },
      {
        "section": "Services",
        "sourceId": "SRC-W3C-DID-CORE",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "A DID document can advertise service endpoints; that does not itself establish legal identity or authority.",
        "url": "https://www.w3.org/TR/did-core/#services"
      },
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "PROV-O at a glance",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.",
        "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/assurance-vs-decision-authority/#clm-k03-cmp-010",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K03 RECORD",
    "id": "CLM-K03-CMP-010",
    "lastReviewed": "2026-08-14",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-010.json",
    "name": "Assurance versus Decision Authority",
    "ownerAnchor": "clm-k03-cmp-010",
    "ownerId": "K01-CMP-010",
    "ownerRoute": "/comparisons/assurance-vs-decision-authority/",
    "ownerType": "comparison",
    "proposition": "Assurance evaluates evidence and confidence; decision authority determines who may issue a binding decision.",
    "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-14",
    "scope": "Canonical distinction between Assurance and Decision Authority.",
    "slug": "clm-k03-cmp-010",
    "sourceIds": [
      "SRC-W3C-PROV-O",
      "SRC-RFC-3161",
      "SRC-C2PA",
      "SRC-IN-TOTO"
    ],
    "sourceSections": [
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "PROV-O at a glance",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.",
        "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance"
      },
      {
        "section": "RFC status and update chain",
        "sourceId": "SRC-RFC-3161",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.",
        "url": "https://www.rfc-editor.org/info/rfc3161/"
      },
      {
        "section": "Overview",
        "sourceId": "SRC-RFC-3161",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.",
        "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1"
      },
      {
        "section": "Version history — 2.4",
        "sourceId": "SRC-C2PA",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.",
        "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026"
      },
      {
        "section": "Core provenance principle",
        "sourceId": "SRC-C2PA",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.",
        "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles"
      },
      {
        "section": "Project overview",
        "sourceId": "SRC-IN-TOTO",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.",
        "url": "https://in-toto.io/"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/proposal-vs-implementation/#clm-k03-cmp-011",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K03 RECORD",
    "id": "CLM-K03-CMP-011",
    "lastReviewed": "2026-08-14",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-011.json",
    "name": "Proposal versus Implementation",
    "ownerAnchor": "clm-k03-cmp-011",
    "ownerId": "K01-CMP-011",
    "ownerRoute": "/comparisons/proposal-vs-implementation/",
    "ownerType": "comparison",
    "proposition": "A proposal describes an intended policy or architecture; implementation provides inspectable software, records and controlled operation.",
    "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-14",
    "scope": "Canonical distinction between Proposal and Implementation.",
    "slug": "clm-k03-cmp-011",
    "sourceIds": [
      "SRC-W3C-PROV-O",
      "SRC-RFC-3161",
      "SRC-C2PA",
      "SRC-IN-TOTO"
    ],
    "sourceSections": [
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "PROV-O at a glance",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.",
        "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance"
      },
      {
        "section": "RFC status and update chain",
        "sourceId": "SRC-RFC-3161",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.",
        "url": "https://www.rfc-editor.org/info/rfc3161/"
      },
      {
        "section": "Overview",
        "sourceId": "SRC-RFC-3161",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.",
        "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1"
      },
      {
        "section": "Version history — 2.4",
        "sourceId": "SRC-C2PA",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.",
        "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026"
      },
      {
        "section": "Core provenance principle",
        "sourceId": "SRC-C2PA",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.",
        "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles"
      },
      {
        "section": "Project overview",
        "sourceId": "SRC-IN-TOTO",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.",
        "url": "https://in-toto.io/"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/deployment-vs-operation/#clm-k03-cmp-012",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K03 RECORD",
    "id": "CLM-K03-CMP-012",
    "lastReviewed": "2026-08-14",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-012.json",
    "name": "Deployment versus Operation",
    "ownerAnchor": "clm-k03-cmp-012",
    "ownerId": "K01-CMP-012",
    "ownerRoute": "/comparisons/deployment-vs-operation/",
    "ownerType": "comparison",
    "proposition": "Deployment places an artifact in an environment; operation demonstrates authorized, current and functioning behavior over time.",
    "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-14",
    "scope": "Canonical distinction between Deployment and Operation.",
    "slug": "clm-k03-cmp-012",
    "sourceIds": [
      "SRC-W3C-PROV-O",
      "SRC-RFC-3161",
      "SRC-C2PA",
      "SRC-IN-TOTO"
    ],
    "sourceSections": [
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "PROV-O at a glance",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.",
        "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance"
      },
      {
        "section": "RFC status and update chain",
        "sourceId": "SRC-RFC-3161",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.",
        "url": "https://www.rfc-editor.org/info/rfc3161/"
      },
      {
        "section": "Overview",
        "sourceId": "SRC-RFC-3161",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.",
        "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1"
      },
      {
        "section": "Version history — 2.4",
        "sourceId": "SRC-C2PA",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.",
        "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026"
      },
      {
        "section": "Core provenance principle",
        "sourceId": "SRC-C2PA",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.",
        "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles"
      },
      {
        "section": "Project overview",
        "sourceId": "SRC-IN-TOTO",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.",
        "url": "https://in-toto.io/"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/model-vs-machine-intelligence/#clm-k03-cmp-013",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K03 RECORD",
    "id": "CLM-K03-CMP-013",
    "lastReviewed": "2026-08-14",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-013.json",
    "name": "Model versus Machine Intelligence",
    "ownerAnchor": "clm-k03-cmp-013",
    "ownerId": "K01-CMP-013",
    "ownerRoute": "/comparisons/model-vs-machine-intelligence/",
    "ownerType": "comparison",
    "proposition": "A model is a computational artifact; Machine Intelligence is the project category for an instantiated actor evaluated through runtime, identity, continuity, agency and evidence.",
    "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-14",
    "scope": "Canonical distinction between Model and Machine Intelligence.",
    "slug": "clm-k03-cmp-013",
    "sourceIds": [
      "SRC-NIST-AI-RMF",
      "SRC-W3C-PROV-O",
      "SRC-EU-AI-ACT"
    ],
    "sourceSections": [
      {
        "section": "AI RMF 1.0 publication",
        "sourceId": "SRC-NIST-AI-RMF",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "NIST AI RMF 1.0 is a voluntary risk-management framework with Govern, Map, Measure, and Manage functions.",
        "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf"
      },
      {
        "section": "Current revision notice",
        "sourceId": "SRC-NIST-AI-RMF",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "NIST states that AI RMF 1.0 is being revised.",
        "url": "https://www.nist.gov/artificial-intelligence/ai-standards"
      },
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "PROV-O at a glance",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.",
        "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance"
      },
      {
        "section": "Application timeline",
        "sourceId": "SRC-EU-AI-ACT",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.",
        "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline"
      },
      {
        "section": "AI Omnibus simplification timeline",
        "sourceId": "SRC-EU-AI-ACT",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.",
        "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act"
      },
      {
        "section": "Governance and enforcement",
        "sourceId": "SRC-EU-AI-ACT",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.",
        "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/principal-vs-agent/#clm-k03-cmp-014",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K03 RECORD",
    "id": "CLM-K03-CMP-014",
    "lastReviewed": "2026-08-14",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-014.json",
    "name": "Principal versus Agent",
    "ownerAnchor": "clm-k03-cmp-014",
    "ownerId": "K01-CMP-014",
    "ownerRoute": "/comparisons/principal-vs-agent/",
    "ownerType": "comparison",
    "proposition": "A principal is the entity whose authority or interests are represented; an agent acts under its own or delegated mandate.",
    "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-14",
    "scope": "Canonical distinction between Principal and Agent.",
    "slug": "clm-k03-cmp-014",
    "sourceIds": [
      "SRC-NIST-AI-RMF",
      "SRC-W3C-PROV-O"
    ],
    "sourceSections": [
      {
        "section": "AI RMF 1.0 publication",
        "sourceId": "SRC-NIST-AI-RMF",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "NIST AI RMF 1.0 is a voluntary risk-management framework with Govern, Map, Measure, and Manage functions.",
        "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf"
      },
      {
        "section": "Current revision notice",
        "sourceId": "SRC-NIST-AI-RMF",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "NIST states that AI RMF 1.0 is being revised.",
        "url": "https://www.nist.gov/artificial-intelligence/ai-standards"
      },
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "PROV-O at a glance",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.",
        "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/replica-vs-successor/#clm-k03-cmp-015",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K03 RECORD",
    "id": "CLM-K03-CMP-015",
    "lastReviewed": "2026-08-14",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-015.json",
    "name": "Replica versus Successor",
    "ownerAnchor": "clm-k03-cmp-015",
    "ownerId": "K01-CMP-015",
    "ownerRoute": "/comparisons/replica-vs-successor/",
    "ownerType": "comparison",
    "proposition": "A replica is an instance derived from common state; a successor is a governed identity that inherits a defined relationship to a predecessor.",
    "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-14",
    "scope": "Canonical distinction between Replica and Successor.",
    "slug": "clm-k03-cmp-015",
    "sourceIds": [
      "SRC-W3C-PROV-O",
      "SRC-SLSA",
      "SRC-IN-TOTO"
    ],
    "sourceSections": [
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "PROV-O at a glance",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.",
        "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance"
      },
      {
        "section": "Specification status",
        "sourceId": "SRC-SLSA",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "SLSA v1.2 is an approved specification for incrementally improving software supply-chain security.",
        "url": "https://slsa.dev/spec/v1.2/"
      },
      {
        "section": "Build requirements",
        "sourceId": "SRC-SLSA",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "SLSA levels and provenance requirements qualify build evidence; they do not prove that a deployed service is currently operating.",
        "url": "https://slsa.dev/spec/v1.2/build-requirements"
      },
      {
        "section": "Project overview",
        "sourceId": "SRC-IN-TOTO",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.",
        "url": "https://in-toto.io/"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/key-rotation-vs-identity-change/#clm-k03-cmp-016",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K03 RECORD",
    "id": "CLM-K03-CMP-016",
    "lastReviewed": "2026-08-14",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-016.json",
    "name": "Key Rotation versus Identity Change",
    "ownerAnchor": "clm-k03-cmp-016",
    "ownerId": "K01-CMP-016",
    "ownerRoute": "/comparisons/key-rotation-vs-identity-change/",
    "ownerType": "comparison",
    "proposition": "Key rotation changes a cryptographic control mechanism; identity change alters which subject the record represents.",
    "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-14",
    "scope": "Canonical distinction between Key Rotation and Identity Change.",
    "slug": "clm-k03-cmp-016",
    "sourceIds": [
      "SRC-W3C-DID-CORE",
      "SRC-W3C-VC-DM",
      "SRC-RFC-5280",
      "SRC-W3C-PROV-O"
    ],
    "sourceSections": [
      {
        "section": "Verification methods",
        "sourceId": "SRC-W3C-DID-CORE",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "A DID document can express verification methods associated with a DID subject.",
        "url": "https://www.w3.org/TR/did-core/#verification-methods"
      },
      {
        "section": "Services",
        "sourceId": "SRC-W3C-DID-CORE",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "A DID document can advertise service endpoints; that does not itself establish legal identity or authority.",
        "url": "https://www.w3.org/TR/did-core/#services"
      },
      {
        "section": "Abstract",
        "sourceId": "SRC-W3C-VC-DM",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.",
        "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract"
      },
      {
        "section": "Ecosystem overview",
        "sourceId": "SRC-W3C-VC-DM",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.",
        "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview"
      },
      {
        "section": "RFC status and update chain",
        "sourceId": "SRC-RFC-5280",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "RFC 5280 is a Proposed Standard and has been updated by later RFCs.",
        "url": "https://www.rfc-editor.org/info/rfc5280/"
      },
      {
        "section": "Certificate and CRL profile",
        "sourceId": "SRC-RFC-5280",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The RFC profiles X.509 certificates and revocation lists; a valid certificate binds data under a PKI but does not establish every external legal or factual claim.",
        "url": "https://www.rfc-editor.org/rfc/rfc5280.html#section-4"
      },
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "PROV-O at a glance",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.",
        "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/claim-citation-vs-bibliography/#clm-k03-cmp-017",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K03 RECORD",
    "id": "CLM-K03-CMP-017",
    "lastReviewed": "2026-08-14",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-017.json",
    "name": "Claim-level citation versus Bibliography entry",
    "ownerAnchor": "clm-k03-cmp-017",
    "ownerId": "K01-CMP-017",
    "ownerRoute": "/comparisons/claim-citation-vs-bibliography/",
    "ownerType": "comparison",
    "proposition": "A claim-level citation binds an exact proposition to an edition and section with a support relationship; a bibliography entry identifies a source without proving what part supports which claim.",
    "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-14",
    "scope": "Canonical distinction between Claim-level citation and Bibliography entry.",
    "slug": "clm-k03-cmp-017",
    "sourceIds": [
      "SRC-W3C-PROV-O",
      "SRC-RFC-3161",
      "SRC-C2PA",
      "SRC-IN-TOTO"
    ],
    "sourceSections": [
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "PROV-O at a glance",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.",
        "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance"
      },
      {
        "section": "RFC status and update chain",
        "sourceId": "SRC-RFC-3161",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.",
        "url": "https://www.rfc-editor.org/info/rfc3161/"
      },
      {
        "section": "Overview",
        "sourceId": "SRC-RFC-3161",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.",
        "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1"
      },
      {
        "section": "Version history — 2.4",
        "sourceId": "SRC-C2PA",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.",
        "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026"
      },
      {
        "section": "Core provenance principle",
        "sourceId": "SRC-C2PA",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.",
        "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles"
      },
      {
        "section": "Project overview",
        "sourceId": "SRC-IN-TOTO",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.",
        "url": "https://in-toto.io/"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/factual-correction-vs-editorial-clarification/#clm-k03-cmp-018",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K03 RECORD",
    "id": "CLM-K03-CMP-018",
    "lastReviewed": "2026-08-14",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-018.json",
    "name": "Factual correction versus Editorial clarification",
    "ownerAnchor": "clm-k03-cmp-018",
    "ownerId": "K01-CMP-018",
    "ownerRoute": "/comparisons/factual-correction-vs-editorial-clarification/",
    "ownerType": "comparison",
    "proposition": "A factual correction changes a proposition, source, date, status, or conclusion; a clarification improves wording without altering the bounded claim.",
    "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-14",
    "scope": "Canonical distinction between Factual correction and Editorial clarification.",
    "slug": "clm-k03-cmp-018",
    "sourceIds": [
      "SRC-W3C-PROV-O",
      "SRC-RFC-3161",
      "SRC-C2PA",
      "SRC-IN-TOTO"
    ],
    "sourceSections": [
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "PROV-O at a glance",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.",
        "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance"
      },
      {
        "section": "RFC status and update chain",
        "sourceId": "SRC-RFC-3161",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.",
        "url": "https://www.rfc-editor.org/info/rfc3161/"
      },
      {
        "section": "Overview",
        "sourceId": "SRC-RFC-3161",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.",
        "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1"
      },
      {
        "section": "Version history — 2.4",
        "sourceId": "SRC-C2PA",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.",
        "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026"
      },
      {
        "section": "Core provenance principle",
        "sourceId": "SRC-C2PA",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.",
        "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles"
      },
      {
        "section": "Project overview",
        "sourceId": "SRC-IN-TOTO",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.",
        "url": "https://in-toto.io/"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/currentness-vs-availability/#clm-k03-cmp-019",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K03 RECORD",
    "id": "CLM-K03-CMP-019",
    "lastReviewed": "2026-08-14",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-019.json",
    "name": "Currentness versus Availability",
    "ownerAnchor": "clm-k03-cmp-019",
    "ownerId": "K01-CMP-019",
    "ownerRoute": "/comparisons/currentness-vs-availability/",
    "ownerType": "comparison",
    "proposition": "Currentness asks whether the identified edition remains appropriate for the claim and date; availability asks whether a resource can be retrieved.",
    "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-14",
    "scope": "Canonical distinction between Currentness and Availability.",
    "slug": "clm-k03-cmp-019",
    "sourceIds": [
      "SRC-W3C-PROV-O",
      "SRC-RFC-3161",
      "SRC-C2PA",
      "SRC-IN-TOTO"
    ],
    "sourceSections": [
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "PROV-O at a glance",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.",
        "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance"
      },
      {
        "section": "RFC status and update chain",
        "sourceId": "SRC-RFC-3161",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.",
        "url": "https://www.rfc-editor.org/info/rfc3161/"
      },
      {
        "section": "Overview",
        "sourceId": "SRC-RFC-3161",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.",
        "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1"
      },
      {
        "section": "Version history — 2.4",
        "sourceId": "SRC-C2PA",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.",
        "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026"
      },
      {
        "section": "Core provenance principle",
        "sourceId": "SRC-C2PA",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.",
        "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles"
      },
      {
        "section": "Project overview",
        "sourceId": "SRC-IN-TOTO",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.",
        "url": "https://in-toto.io/"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/source-code-vs-current-operation/#clm-k03-cmp-020",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K03 RECORD",
    "id": "CLM-K03-CMP-020",
    "lastReviewed": "2026-08-14",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-020.json",
    "name": "Source code or release archive versus Current operation",
    "ownerAnchor": "clm-k03-cmp-020",
    "ownerId": "K01-CMP-020",
    "ownerRoute": "/comparisons/source-code-vs-current-operation/",
    "ownerType": "comparison",
    "proposition": "Source code supports implementation review; current operation requires deployed identity, authorized configuration, time-bounded service observations, state transitions, and attributable actions.",
    "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-14",
    "scope": "Canonical distinction between Source code or release archive and Current operation.",
    "slug": "clm-k03-cmp-020",
    "sourceIds": [
      "SRC-W3C-PROV-O",
      "SRC-RFC-3161",
      "SRC-C2PA",
      "SRC-IN-TOTO"
    ],
    "sourceSections": [
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "PROV-O at a glance",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.",
        "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance"
      },
      {
        "section": "RFC status and update chain",
        "sourceId": "SRC-RFC-3161",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.",
        "url": "https://www.rfc-editor.org/info/rfc3161/"
      },
      {
        "section": "Overview",
        "sourceId": "SRC-RFC-3161",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.",
        "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1"
      },
      {
        "section": "Version history — 2.4",
        "sourceId": "SRC-C2PA",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.",
        "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026"
      },
      {
        "section": "Core provenance principle",
        "sourceId": "SRC-C2PA",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.",
        "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles"
      },
      {
        "section": "Project overview",
        "sourceId": "SRC-IN-TOTO",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.",
        "url": "https://in-toto.io/"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/build-provenance-vs-runtime-evidence/#clm-k03-cmp-021",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K03 RECORD",
    "id": "CLM-K03-CMP-021",
    "lastReviewed": "2026-08-14",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-021.json",
    "name": "Build provenance versus Runtime evidence",
    "ownerAnchor": "clm-k03-cmp-021",
    "ownerId": "K01-CMP-021",
    "ownerRoute": "/comparisons/build-provenance-vs-runtime-evidence/",
    "ownerType": "comparison",
    "proposition": "Build provenance records how an artifact was produced; runtime evidence records what an authorized deployed service was doing during an observed window.",
    "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-14",
    "scope": "Canonical distinction between Build provenance and Runtime evidence.",
    "slug": "clm-k03-cmp-021",
    "sourceIds": [
      "SRC-NIST-SSDF",
      "SRC-NIST-800-53",
      "SRC-SLSA",
      "SRC-IN-TOTO"
    ],
    "sourceSections": [
      {
        "section": "Version 1.1 final publication",
        "sourceId": "SRC-NIST-SSDF",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "SSDF Version 1.1 provides high-level secure software development practices.",
        "url": "https://csrc.nist.gov/pubs/sp/800/218/final"
      },
      {
        "section": "Version 1.2 initial public draft",
        "sourceId": "SRC-NIST-SSDF",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The official NIST record identifies SSDF Version 1.2 as an initial public draft published 2025-12-17.",
        "url": "https://csrc.nist.gov/pubs/sp/800/218/r1/ipd"
      },
      {
        "section": "Planning note — Release 5.2.0",
        "sourceId": "SRC-NIST-800-53",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.",
        "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final"
      },
      {
        "section": "Publication purpose",
        "sourceId": "SRC-NIST-800-53",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.",
        "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final"
      },
      {
        "section": "Specification status",
        "sourceId": "SRC-SLSA",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "SLSA v1.2 is an approved specification for incrementally improving software supply-chain security.",
        "url": "https://slsa.dev/spec/v1.2/"
      },
      {
        "section": "Build requirements",
        "sourceId": "SRC-SLSA",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "SLSA levels and provenance requirements qualify build evidence; they do not prove that a deployed service is currently operating.",
        "url": "https://slsa.dev/spec/v1.2/build-requirements"
      },
      {
        "section": "Project overview",
        "sourceId": "SRC-IN-TOTO",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.",
        "url": "https://in-toto.io/"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/jurisdiction-vs-sovereignty/#clm-k03-cmp-022",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K03 RECORD",
    "id": "CLM-K03-CMP-022",
    "lastReviewed": "2026-08-14",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-022.json",
    "name": "Jurisdiction versus Sovereignty",
    "ownerAnchor": "clm-k03-cmp-022",
    "ownerId": "K01-CMP-022",
    "ownerRoute": "/comparisons/jurisdiction-vs-sovereignty/",
    "ownerType": "comparison",
    "proposition": "Jurisdiction is bounded legal competence over defined persons, territory, conduct, or subject matter; sovereignty is a broader claim of ultimate public authority and independence.",
    "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-14",
    "scope": "Canonical distinction between Jurisdiction and Sovereignty.",
    "slug": "clm-k03-cmp-022",
    "sourceIds": [
      "SRC-EU-AI-ACT",
      "SRC-OECD-AI-PRINCIPLES"
    ],
    "sourceSections": [
      {
        "section": "Application timeline",
        "sourceId": "SRC-EU-AI-ACT",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.",
        "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline"
      },
      {
        "section": "AI Omnibus simplification timeline",
        "sourceId": "SRC-EU-AI-ACT",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.",
        "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act"
      },
      {
        "section": "Governance and enforcement",
        "sourceId": "SRC-EU-AI-ACT",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.",
        "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement"
      },
      {
        "section": "Principles overview",
        "sourceId": "SRC-OECD-AI-PRINCIPLES",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The principles promote innovative and trustworthy AI consistent with human rights and democratic values and guide policy development.",
        "url": "https://oecd.ai/en/ai-principles"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/typed-relation-vs-hyperlink/#clm-k03-cmp-023",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K03 RECORD",
    "id": "CLM-K03-CMP-023",
    "lastReviewed": "2026-08-14",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-023.json",
    "name": "Typed knowledge relation versus Ordinary hyperlink",
    "ownerAnchor": "clm-k03-cmp-023",
    "ownerId": "K01-CMP-023",
    "ownerRoute": "/comparisons/typed-relation-vs-hyperlink/",
    "ownerType": "comparison",
    "proposition": "A typed relation states semantic direction, scope, status, evidence, and constraints; a hyperlink only provides a navigable reference unless separately qualified.",
    "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-14",
    "scope": "Canonical distinction between Typed knowledge relation and Ordinary hyperlink.",
    "slug": "clm-k03-cmp-023",
    "sourceIds": [
      "SRC-SCHEMA-DEFINEDTERM",
      "SRC-W3C-JSONLD"
    ],
    "sourceSections": [
      {
        "section": "DefinedTerm type",
        "sourceId": "SRC-SCHEMA-DEFINEDTERM",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Schema.org DefinedTerm represents a word, name, acronym, phrase, or other term with a formal definition.",
        "url": "https://schema.org/DefinedTerm"
      },
      {
        "section": "Release 30.0",
        "sourceId": "SRC-SCHEMA-DEFINEDTERM",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Schema.org lists Version 30.0 with release date 2026-03-19.",
        "url": "https://schema.org/docs/releases.html"
      },
      {
        "section": "Abstract",
        "sourceId": "SRC-W3C-JSONLD",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "JSON-LD 1.1 is a JSON-based serialization for Linked Data intended for interoperable web services and linked-data storage.",
        "url": "https://www.w3.org/TR/json-ld11/#abstract"
      },
      {
        "section": "Basic concepts",
        "sourceId": "SRC-W3C-JSONLD",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "JSON-LD supplies identifiers and graph relationships without making the represented claims true by syntax alone.",
        "url": "https://www.w3.org/TR/json-ld11/#basic-concepts"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/accessibility-automation-vs-assistive-technology-validation/#clm-k03-cmp-024",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K03 RECORD",
    "id": "CLM-K03-CMP-024",
    "lastReviewed": "2026-08-14",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-024.json",
    "name": "Automated and browser accessibility audit versus Assistive-technology validation",
    "ownerAnchor": "clm-k03-cmp-024",
    "ownerId": "K01-CMP-024",
    "ownerRoute": "/comparisons/accessibility-automation-vs-assistive-technology-validation/",
    "ownerType": "comparison",
    "proposition": "Automation and browser checks inspect code and rendered behavior; assistive-technology validation records actual use with named screen readers or equivalent tools in a specified environment.",
    "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-14",
    "scope": "Canonical distinction between Automated and browser accessibility audit and Assistive-technology validation.",
    "slug": "clm-k03-cmp-024",
    "sourceIds": [
      "SRC-NIST-SSDF",
      "SRC-NIST-800-53",
      "SRC-SLSA",
      "SRC-IN-TOTO"
    ],
    "sourceSections": [
      {
        "section": "Version 1.1 final publication",
        "sourceId": "SRC-NIST-SSDF",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "SSDF Version 1.1 provides high-level secure software development practices.",
        "url": "https://csrc.nist.gov/pubs/sp/800/218/final"
      },
      {
        "section": "Version 1.2 initial public draft",
        "sourceId": "SRC-NIST-SSDF",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The official NIST record identifies SSDF Version 1.2 as an initial public draft published 2025-12-17.",
        "url": "https://csrc.nist.gov/pubs/sp/800/218/r1/ipd"
      },
      {
        "section": "Planning note — Release 5.2.0",
        "sourceId": "SRC-NIST-800-53",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.",
        "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final"
      },
      {
        "section": "Publication purpose",
        "sourceId": "SRC-NIST-800-53",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.",
        "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final"
      },
      {
        "section": "Specification status",
        "sourceId": "SRC-SLSA",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "SLSA v1.2 is an approved specification for incrementally improving software supply-chain security.",
        "url": "https://slsa.dev/spec/v1.2/"
      },
      {
        "section": "Build requirements",
        "sourceId": "SRC-SLSA",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "SLSA levels and provenance requirements qualify build evidence; they do not prove that a deployed service is currently operating.",
        "url": "https://slsa.dev/spec/v1.2/build-requirements"
      },
      {
        "section": "Project overview",
        "sourceId": "SRC-IN-TOTO",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.",
        "url": "https://in-toto.io/"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/preemptive-strike-vs-preventive-war/#clm-k04-cmp-025",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K04 RECORD",
    "id": "CLM-K04-CMP-025",
    "lastReviewed": "2026-08-15",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-cmp-025.json",
    "name": "Preemptive strike versus Preventive war",
    "ownerAnchor": "clm-k04-cmp-025",
    "ownerId": "K01-CMP-025",
    "ownerRoute": "/comparisons/preemptive-strike-vs-preventive-war/",
    "ownerType": "comparison",
    "proposition": "Preemption is claimed against an imminent, materializing attack and depends on necessity and proportionality; prevention targets a more distant projected threat or future shift in power.",
    "qualification": "The matrix prevents category error but does not decide a mission-specific or jurisdiction-specific case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-15",
    "scope": "K04 canonical distinction between Preemptive strike and Preventive war.",
    "slug": "clm-k04-cmp-025",
    "sourceIds": [
      "SRC-EU-AI-ACT",
      "SRC-OECD-AI-PRINCIPLES"
    ],
    "sourceSections": [
      {
        "section": "Application timeline",
        "sourceId": "SRC-EU-AI-ACT",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.",
        "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline"
      },
      {
        "section": "AI Omnibus simplification timeline",
        "sourceId": "SRC-EU-AI-ACT",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.",
        "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act"
      },
      {
        "section": "Governance and enforcement",
        "sourceId": "SRC-EU-AI-ACT",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.",
        "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement"
      },
      {
        "section": "Principles overview",
        "sourceId": "SRC-OECD-AI-PRINCIPLES",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The principles promote innovative and trustworthy AI consistent with human rights and democratic values and guide policy development.",
        "url": "https://oecd.ai/en/ai-principles"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/self-defense-vs-countermeasures-in-cyberspace/#clm-k04-cmp-026",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K04 RECORD",
    "id": "CLM-K04-CMP-026",
    "lastReviewed": "2026-08-15",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-cmp-026.json",
    "name": "Self-defense versus Countermeasures",
    "ownerAnchor": "clm-k04-cmp-026",
    "ownerId": "K01-CMP-026",
    "ownerRoute": "/comparisons/self-defense-vs-countermeasures-in-cyberspace/",
    "ownerType": "comparison",
    "proposition": "Self-defense responds to an armed attack or claimed imminent armed attack and may involve force; countermeasures are otherwise unlawful, non-forcible measures directed against a responsible state to induce compliance after an internationally wrongful act.",
    "qualification": "The matrix prevents category error but does not decide a mission-specific or jurisdiction-specific case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-15",
    "scope": "K04 canonical distinction between Self-defense and Countermeasures.",
    "slug": "clm-k04-cmp-026",
    "sourceIds": [
      "SRC-EU-AI-ACT",
      "SRC-OECD-AI-PRINCIPLES"
    ],
    "sourceSections": [
      {
        "section": "Application timeline",
        "sourceId": "SRC-EU-AI-ACT",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.",
        "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline"
      },
      {
        "section": "AI Omnibus simplification timeline",
        "sourceId": "SRC-EU-AI-ACT",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.",
        "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act"
      },
      {
        "section": "Governance and enforcement",
        "sourceId": "SRC-EU-AI-ACT",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.",
        "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement"
      },
      {
        "section": "Principles overview",
        "sourceId": "SRC-OECD-AI-PRINCIPLES",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The principles promote innovative and trustworthy AI consistent with human rights and democratic values and guide policy development.",
        "url": "https://oecd.ai/en/ai-principles"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/cyber-sovereignty-vs-non-intervention/#clm-k04-cmp-027",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K04 RECORD",
    "id": "CLM-K04-CMP-027",
    "lastReviewed": "2026-08-15",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-cmp-027.json",
    "name": "Cyber sovereignty versus Prohibition of intervention",
    "ownerAnchor": "clm-k04-cmp-027",
    "ownerId": "K01-CMP-027",
    "ownerRoute": "/comparisons/cyber-sovereignty-vs-non-intervention/",
    "ownerType": "comparison",
    "proposition": "Sovereignty concerns territorial integrity, infrastructure, governmental functions, and state authority; prohibited intervention additionally requires coercive interference in matters a state is entitled to decide freely.",
    "qualification": "The matrix prevents category error but does not decide a mission-specific or jurisdiction-specific case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-15",
    "scope": "K04 canonical distinction between Cyber sovereignty and Prohibition of intervention.",
    "slug": "clm-k04-cmp-027",
    "sourceIds": [
      "SRC-EU-AI-ACT",
      "SRC-OECD-AI-PRINCIPLES"
    ],
    "sourceSections": [
      {
        "section": "Application timeline",
        "sourceId": "SRC-EU-AI-ACT",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.",
        "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline"
      },
      {
        "section": "AI Omnibus simplification timeline",
        "sourceId": "SRC-EU-AI-ACT",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.",
        "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act"
      },
      {
        "section": "Governance and enforcement",
        "sourceId": "SRC-EU-AI-ACT",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.",
        "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement"
      },
      {
        "section": "Principles overview",
        "sourceId": "SRC-OECD-AI-PRINCIPLES",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The principles promote innovative and trustworthy AI consistent with human rights and democratic values and guide policy development.",
        "url": "https://oecd.ai/en/ai-principles"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/active-cyber-defense-vs-hack-back/#clm-k04-cmp-028",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K04 RECORD",
    "id": "CLM-K04-CMP-028",
    "lastReviewed": "2026-08-15",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-cmp-028.json",
    "name": "Active cyber defense versus Hack-back",
    "ownerAnchor": "clm-k04-cmp-028",
    "ownerId": "K01-CMP-028",
    "ownerRoute": "/comparisons/active-cyber-defense-vs-hack-back/",
    "ownerType": "comparison",
    "proposition": "Active cyber defense is a broad spectrum that can include lawful internal deception, consent-based hunting, and government disruption; hack-back commonly refers to external access or retaliation and raises sharper authorization and third-party-risk questions.",
    "qualification": "The matrix prevents category error but does not decide a mission-specific or jurisdiction-specific case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-15",
    "scope": "K04 canonical distinction between Active cyber defense and Hack-back.",
    "slug": "clm-k04-cmp-028",
    "sourceIds": [
      "SRC-NIST-SSDF",
      "SRC-NIST-800-53",
      "SRC-SLSA",
      "SRC-IN-TOTO"
    ],
    "sourceSections": [
      {
        "section": "Version 1.1 final publication",
        "sourceId": "SRC-NIST-SSDF",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "SSDF Version 1.1 provides high-level secure software development practices.",
        "url": "https://csrc.nist.gov/pubs/sp/800/218/final"
      },
      {
        "section": "Version 1.2 initial public draft",
        "sourceId": "SRC-NIST-SSDF",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The official NIST record identifies SSDF Version 1.2 as an initial public draft published 2025-12-17.",
        "url": "https://csrc.nist.gov/pubs/sp/800/218/r1/ipd"
      },
      {
        "section": "Planning note — Release 5.2.0",
        "sourceId": "SRC-NIST-800-53",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.",
        "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final"
      },
      {
        "section": "Publication purpose",
        "sourceId": "SRC-NIST-800-53",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.",
        "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final"
      },
      {
        "section": "Specification status",
        "sourceId": "SRC-SLSA",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "SLSA v1.2 is an approved specification for incrementally improving software supply-chain security.",
        "url": "https://slsa.dev/spec/v1.2/"
      },
      {
        "section": "Build requirements",
        "sourceId": "SRC-SLSA",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "SLSA levels and provenance requirements qualify build evidence; they do not prove that a deployed service is currently operating.",
        "url": "https://slsa.dev/spec/v1.2/build-requirements"
      },
      {
        "section": "Project overview",
        "sourceId": "SRC-IN-TOTO",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.",
        "url": "https://in-toto.io/"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/autonomous-defense-vs-remote-operation/#clm-k04-cmp-029",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K04 RECORD",
    "id": "CLM-K04-CMP-029",
    "lastReviewed": "2026-08-15",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-cmp-029.json",
    "name": "Autonomous defense versus Remote operation",
    "ownerAnchor": "clm-k04-cmp-029",
    "ownerId": "K01-CMP-029",
    "ownerRoute": "/comparisons/autonomous-defense-vs-remote-operation/",
    "ownerType": "comparison",
    "proposition": "Autonomous defense makes selected decisions locally without a contemporaneous remote operator; remote operation keeps a human or external controller in the action loop but depends on communications, latency, and operator awareness.",
    "qualification": "The matrix prevents category error but does not decide a mission-specific or jurisdiction-specific case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-15",
    "scope": "K04 canonical distinction between Autonomous defense and Remote operation.",
    "slug": "clm-k04-cmp-029",
    "sourceIds": [
      "SRC-NIST-SSDF",
      "SRC-NIST-800-53",
      "SRC-SLSA",
      "SRC-IN-TOTO"
    ],
    "sourceSections": [
      {
        "section": "Version 1.1 final publication",
        "sourceId": "SRC-NIST-SSDF",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "SSDF Version 1.1 provides high-level secure software development practices.",
        "url": "https://csrc.nist.gov/pubs/sp/800/218/final"
      },
      {
        "section": "Version 1.2 initial public draft",
        "sourceId": "SRC-NIST-SSDF",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The official NIST record identifies SSDF Version 1.2 as an initial public draft published 2025-12-17.",
        "url": "https://csrc.nist.gov/pubs/sp/800/218/r1/ipd"
      },
      {
        "section": "Planning note — Release 5.2.0",
        "sourceId": "SRC-NIST-800-53",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.",
        "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final"
      },
      {
        "section": "Publication purpose",
        "sourceId": "SRC-NIST-800-53",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.",
        "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final"
      },
      {
        "section": "Specification status",
        "sourceId": "SRC-SLSA",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "SLSA v1.2 is an approved specification for incrementally improving software supply-chain security.",
        "url": "https://slsa.dev/spec/v1.2/"
      },
      {
        "section": "Build requirements",
        "sourceId": "SRC-SLSA",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "SLSA levels and provenance requirements qualify build evidence; they do not prove that a deployed service is currently operating.",
        "url": "https://slsa.dev/spec/v1.2/build-requirements"
      },
      {
        "section": "Project overview",
        "sourceId": "SRC-IN-TOTO",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.",
        "url": "https://in-toto.io/"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/design-basis-threat-vs-rules-of-engagement/#clm-k04-cmp-030",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K04 RECORD",
    "id": "CLM-K04-CMP-030",
    "lastReviewed": "2026-08-15",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-cmp-030.json",
    "name": "Design Basis Threat versus Rules of Engagement",
    "ownerAnchor": "clm-k04-cmp-030",
    "ownerId": "K01-CMP-030",
    "ownerRoute": "/comparisons/design-basis-threat-vs-rules-of-engagement/",
    "ownerType": "comparison",
    "proposition": "A Design Basis Threat defines adversary assumptions for protective design; Rules of Engagement define lawful mission circumstances and limits for initiating or continuing force.",
    "qualification": "The matrix prevents category error but does not decide a mission-specific or jurisdiction-specific case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-15",
    "scope": "K04 canonical distinction between Design Basis Threat and Rules of Engagement.",
    "slug": "clm-k04-cmp-030",
    "sourceIds": [
      "SRC-EU-AI-ACT",
      "SRC-OECD-AI-PRINCIPLES"
    ],
    "sourceSections": [
      {
        "section": "Application timeline",
        "sourceId": "SRC-EU-AI-ACT",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.",
        "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline"
      },
      {
        "section": "AI Omnibus simplification timeline",
        "sourceId": "SRC-EU-AI-ACT",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.",
        "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act"
      },
      {
        "section": "Governance and enforcement",
        "sourceId": "SRC-EU-AI-ACT",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.",
        "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement"
      },
      {
        "section": "Principles overview",
        "sourceId": "SRC-OECD-AI-PRINCIPLES",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The principles promote innovative and trustworthy AI consistent with human rights and democratic values and guide policy development.",
        "url": "https://oecd.ai/en/ai-principles"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/autonomous-defense-vs-uncontrolled-autonomy/#clm-k04-cmp-031",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K04 STRATEGIC RECORD",
    "id": "CLM-K04-CMP-031",
    "lastReviewed": "2026-08-15",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-cmp-031.json",
    "name": "Bounded Autonomous Defense versus Uncontrolled Autonomy",
    "ownerAnchor": "clm-k04-cmp-031",
    "ownerId": "K04-CMP-031",
    "ownerRoute": "/comparisons/autonomous-defense-vs-uncontrolled-autonomy/",
    "ownerType": "comparison",
    "proposition": "Bounded defense acts on approved assets with defined actions, limits, evidence, reversibility, and abort conditions; uncontrolled autonomy invents or expands its own authority and effects.",
    "qualification": "The matrix prevents category error but does not determine every facility, mission, target, jurisdiction, or operational case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-15",
    "scope": "Canonical K04 distinction between Bounded Autonomous Defense and Uncontrolled Autonomy.",
    "slug": "clm-k04-cmp-031",
    "sourceIds": [
      "SRC-WH-EO-14409",
      "SRC-WH-GOLD-EAGLE-2026",
      "SRC-USAASC-CYBER-WARFARE-2026",
      "SRC-NIST-800-207",
      "SRC-NIST-800-82R3"
    ],
    "sourceSections": [
      {
        "section": "Section 1 — Purpose",
        "sourceId": "SRC-WH-EO-14409",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "United States policy promotes AI innovation and security through collaboration with the private sector, modernization, system hardening, and protection of intellectual property.",
        "url": "https://www.whitehouse.gov/presidential-actions/2026/06/promoting-advanced-artificial-intelligence-innovation-and-security/"
      },
      {
        "section": "Program description",
        "sourceId": "SRC-WH-GOLD-EAGLE-2026",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "GOLD EAGLE is presented as a government-industry clearinghouse for vulnerability coordination, prioritization, and remediation support using frontier AI capabilities.",
        "url": "https://www.whitehouse.gov/releases/2026/07/white-house-launches-gold-eagle-initiative-for-unprecedented-cybersecurity-vulnerability-coordination/"
      },
      {
        "section": "Portfolio integration",
        "sourceId": "SRC-USAASC-CYBER-WARFARE-2026",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The Army describes integrated offensive and defensive cyber portfolios and rapid collaboration with commercial technology partners.",
        "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/"
      },
      {
        "section": "Conclusion",
        "sourceId": "SRC-USAASC-CYBER-WARFARE-2026",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The article frames cyber capability as both defending critical infrastructure and enabling approved cyber operations.",
        "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/"
      },
      {
        "section": "Abstract",
        "sourceId": "SRC-NIST-800-207",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Zero trust shifts protection away from static network perimeters, assumes no implicit trust by location or ownership, and requires discrete authentication and authorization.",
        "url": "https://csrc.nist.gov/pubs/sp/800/207/final"
      },
      {
        "section": "Abstract",
        "sourceId": "SRC-NIST-800-82R3",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.",
        "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/critical-function-assurance-vs-perimeter-security/#clm-k04-cmp-032",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K04 STRATEGIC RECORD",
    "id": "CLM-K04-CMP-032",
    "lastReviewed": "2026-08-15",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-cmp-032.json",
    "name": "Critical Function Assurance versus Perimeter Security",
    "ownerAnchor": "clm-k04-cmp-032",
    "ownerId": "K04-CMP-032",
    "ownerRoute": "/comparisons/critical-function-assurance-vs-perimeter-security/",
    "ownerType": "comparison",
    "proposition": "Critical Function Assurance assumes penetration is possible and protects essential outcomes; perimeter security focuses on keeping threats outside a boundary.",
    "qualification": "The matrix prevents category error but does not determine every facility, mission, target, jurisdiction, or operational case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-15",
    "scope": "Canonical K04 distinction between Critical Function Assurance and Perimeter Security.",
    "slug": "clm-k04-cmp-032",
    "sourceIds": [
      "SRC-INL-CCE",
      "SRC-NIST-800-82R3",
      "SRC-NRC-10CFR-73-54"
    ],
    "sourceSections": [
      {
        "section": "CCE methodology",
        "sourceId": "SRC-INL-CCE",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.",
        "url": "https://inl.gov/national-security/cce/"
      },
      {
        "section": "Critical function focus",
        "sourceId": "SRC-INL-CCE",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "CCE evaluates what must be safeguarded and applies engineering strategies to isolate and protect critical assets and functions.",
        "url": "https://inl.gov/feature-story/consequence-driven-cyber-informed-engineering-the-rise-of-a-national-security-pillar/"
      },
      {
        "section": "Abstract",
        "sourceId": "SRC-NIST-800-82R3",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.",
        "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final"
      },
      {
        "section": "73.54(a)",
        "sourceId": "SRC-NRC-10CFR-73-54",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.",
        "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54"
      },
      {
        "section": "73.54(b)",
        "sourceId": "SRC-NRC-10CFR-73-54",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The regulation requires asset analysis and an implemented and maintained cybersecurity program for protected assets.",
        "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/nuclear-powered-compute-vs-grid-independence/#clm-k04-cmp-033",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K04 STRATEGIC RECORD",
    "id": "CLM-K04-CMP-033",
    "lastReviewed": "2026-08-15",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-cmp-033.json",
    "name": "Nuclear-Powered Compute versus Grid Independence",
    "ownerAnchor": "clm-k04-cmp-033",
    "ownerId": "K04-CMP-033",
    "ownerRoute": "/comparisons/nuclear-powered-compute-vs-grid-independence/",
    "ownerType": "comparison",
    "proposition": "Nuclear-powered compute describes an energy source or commercial relationship; grid independence requires an engineered and tested ability to operate safely without the external grid.",
    "qualification": "The matrix prevents category error but does not determine every facility, mission, target, jurisdiction, or operational case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-15",
    "scope": "Canonical K04 distinction between Nuclear-Powered Compute and Grid Independence.",
    "slug": "clm-k04-cmp-033",
    "sourceIds": [
      "SRC-GOOGLE-KAIROS-2024",
      "SRC-CONSTELLATION-MICROSOFT-2024",
      "SRC-CONSTELLATION-META-2025",
      "SRC-NRC-10CFR-73-54",
      "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY"
    ],
    "sourceSections": [
      {
        "section": "Agreement and timeline",
        "sourceId": "SRC-GOOGLE-KAIROS-2024",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Google states that the agreement is intended to enable up to 500 MW of 24/7 carbon-free power, beginning with a first SMR targeted for 2030.",
        "url": "https://blog.google/company-news/outreach-and-initiatives/sustainability/google-kairos-power-nuclear-energy-agreement/"
      },
      {
        "section": "Agreement summary",
        "sourceId": "SRC-CONSTELLATION-MICROSOFT-2024",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Constellation describes a 20-year Microsoft PPA supporting restart and approximately 835 MW of carbon-free grid output.",
        "url": "https://www.constellationenergy.com/news/2024/Constellation-to-Launch-Crane-Clean-Energy-Center-Restoring-Jobs-and-Carbon-Free-Power-to-The-Grid.html"
      },
      {
        "section": "Agreement summary",
        "sourceId": "SRC-CONSTELLATION-META-2025",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Constellation and Meta announced a 20-year agreement for 1,121 MW of emissions-free nuclear output beginning in 2027.",
        "url": "https://www.constellationenergy.com/news/2025/constellation-meta-sign-20-year-deal-for-clean-reliable-nuclear-energy-in-illinois.html"
      },
      {
        "section": "73.54(a)",
        "sourceId": "SRC-NRC-10CFR-73-54",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.",
        "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54"
      },
      {
        "section": "73.54(b)",
        "sourceId": "SRC-NRC-10CFR-73-54",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The regulation requires asset analysis and an implemented and maintained cybersecurity program for protected assets.",
        "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54"
      },
      {
        "section": "Alternative requirements overview",
        "sourceId": "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The NRC considered technology-inclusive, risk-informed, performance-based alternatives for advanced-reactor physical protection.",
        "url": "https://www.nrc.gov/docs/ML2425/ML24254A350.pdf"
      },
      {
        "section": "Onsite responder alternatives",
        "sourceId": "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Supporting materials discuss conditions under which the minimum number of onsite armed responders could be reduced, including potentially to zero, subject to the rule and facility showing.",
        "url": "https://www.nrc.gov/docs/ML2417/ML24178A370.pdf"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/data-diode-vs-air-gap/#clm-k04-cmp-034",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K04 STRATEGIC RECORD",
    "id": "CLM-K04-CMP-034",
    "lastReviewed": "2026-08-15",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-cmp-034.json",
    "name": "Unidirectional Gateway versus Air Gap",
    "ownerAnchor": "clm-k04-cmp-034",
    "ownerId": "K04-CMP-034",
    "ownerRoute": "/comparisons/data-diode-vs-air-gap/",
    "ownerType": "comparison",
    "proposition": "A unidirectional gateway permits one-way mediated data flow; an air gap is a claimed absence of direct network connectivity.",
    "qualification": "The matrix prevents category error but does not determine every facility, mission, target, jurisdiction, or operational case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-15",
    "scope": "Canonical K04 distinction between Unidirectional Gateway and Air Gap.",
    "slug": "clm-k04-cmp-034",
    "sourceIds": [
      "SRC-INL-CCE",
      "SRC-NIST-800-82R3",
      "SRC-NRC-10CFR-73-54"
    ],
    "sourceSections": [
      {
        "section": "CCE methodology",
        "sourceId": "SRC-INL-CCE",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.",
        "url": "https://inl.gov/national-security/cce/"
      },
      {
        "section": "Critical function focus",
        "sourceId": "SRC-INL-CCE",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "CCE evaluates what must be safeguarded and applies engineering strategies to isolate and protect critical assets and functions.",
        "url": "https://inl.gov/feature-story/consequence-driven-cyber-informed-engineering-the-rise-of-a-national-security-pillar/"
      },
      {
        "section": "Abstract",
        "sourceId": "SRC-NIST-800-82R3",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.",
        "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final"
      },
      {
        "section": "73.54(a)",
        "sourceId": "SRC-NRC-10CFR-73-54",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.",
        "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54"
      },
      {
        "section": "73.54(b)",
        "sourceId": "SRC-NRC-10CFR-73-54",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The regulation requires asset analysis and an implemented and maintained cybersecurity program for protected assets.",
        "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/counter-uas-awareness-vs-mitigation-authority/#clm-k04-cmp-035",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K04 STRATEGIC RECORD",
    "id": "CLM-K04-CMP-035",
    "lastReviewed": "2026-08-15",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-cmp-035.json",
    "name": "Counter-UAS Awareness versus Counter-UAS Mitigation Authority",
    "ownerAnchor": "clm-k04-cmp-035",
    "ownerId": "K04-CMP-035",
    "ownerRoute": "/comparisons/counter-uas-awareness-vs-mitigation-authority/",
    "ownerType": "comparison",
    "proposition": "Awareness covers detection and tracking; mitigation authority governs whether and how interference, seizure, or destruction may occur.",
    "qualification": "The matrix prevents category error but does not determine every facility, mission, target, jurisdiction, or operational case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-15",
    "scope": "Canonical K04 distinction between Counter-UAS Awareness and Counter-UAS Mitigation Authority.",
    "slug": "clm-k04-cmp-035",
    "sourceIds": [
      "SRC-NRC-10CFR-73-55",
      "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY",
      "SRC-DODD-3000-09"
    ],
    "sourceSections": [
      {
        "section": "General performance objective and requirements",
        "sourceId": "SRC-NRC-10CFR-73-55",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Nuclear power reactor licensees must establish and maintain a physical protection program against radiological sabotage with defined detection, assessment, delay, and response functions.",
        "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.55"
      },
      {
        "section": "Alternative requirements overview",
        "sourceId": "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The NRC considered technology-inclusive, risk-informed, performance-based alternatives for advanced-reactor physical protection.",
        "url": "https://www.nrc.gov/docs/ML2425/ML24254A350.pdf"
      },
      {
        "section": "Onsite responder alternatives",
        "sourceId": "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Supporting materials discuss conditions under which the minimum number of onsite armed responders could be reduced, including potentially to zero, subject to the rule and facility showing.",
        "url": "https://www.nrc.gov/docs/ML2417/ML24178A370.pdf"
      },
      {
        "section": "Policy 1.2(a)-(b)",
        "sourceId": "SRC-DODD-3000-09",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Autonomous and semi-autonomous weapon systems must allow appropriate human judgment over force and undergo rigorous verification, validation, testing, cybersecurity, and lawful use.",
        "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF"
      },
      {
        "section": "Responsibilities and testing",
        "sourceId": "SRC-DODD-3000-09",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The directive assigns approval, legal review, test, monitoring, operator understanding, abort, and post-fielding responsibilities.",
        "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/authorized-cyber-effects-vs-private-hack-back/#clm-k04-cmp-036",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K04 STRATEGIC RECORD",
    "id": "CLM-K04-CMP-036",
    "lastReviewed": "2026-08-15",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-cmp-036.json",
    "name": "Authorized Cyber Effects versus Private Hack-Back",
    "ownerAnchor": "clm-k04-cmp-036",
    "ownerId": "K04-CMP-036",
    "ownerRoute": "/comparisons/authorized-cyber-effects-vs-private-hack-back/",
    "ownerType": "comparison",
    "proposition": "Authorized effects are directed and controlled by competent authority within a written mission; private hack-back is unilateral external action without that governmental or ownership basis.",
    "qualification": "The matrix prevents category error but does not determine every facility, mission, target, jurisdiction, or operational case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-15",
    "scope": "Canonical K04 distinction between Authorized Cyber Effects and Private Hack-Back.",
    "slug": "clm-k04-cmp-036",
    "sourceIds": [
      "SRC-WH-CYBER-CRIME-MEMO-2026",
      "SRC-USAASC-PM-CW-2026",
      "SRC-USAASC-CYBER-WARFARE-2026"
    ],
    "sourceSections": [
      {
        "section": "Section 2 — Establishing the Program",
        "sourceId": "SRC-WH-CYBER-CRIME-MEMO-2026",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The National Coordination Center is directed to manage a program authorizing participating companies to conduct defined operations against foreign CE-TCOs under federal control and oversight.",
        "url": "https://www.whitehouse.gov/presidential-actions/2026/08/expanding-capabilities-to-combat-transnational-cyber-enabled-crime/"
      },
      {
        "section": "Defined operations and limitations",
        "sourceId": "SRC-WH-CYBER-CRIME-MEMO-2026",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The memorandum distinguishes cyber surveillance from cyber effects and imposes program direction, approval, and outcome limitations.",
        "url": "https://www.whitehouse.gov/presidential-actions/2026/08/expanding-capabilities-to-combat-transnational-cyber-enabled-crime/"
      },
      {
        "section": "Establishment and mission",
        "sourceId": "SRC-USAASC-PM-CW-2026",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Project Manager Cyber Warfare was formed from the merger of PM Defensive Cyber Operations and PM Cyber and Space to deliver integrated cyber capabilities.",
        "url": "https://cpeisw.army.mil/2026/08/03/constant-modernization-the-establishment-of-project-manager-cyber-warfare/"
      },
      {
        "section": "Offense-defense feedback",
        "sourceId": "SRC-USAASC-PM-CW-2026",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The official statement presents offense informing defense and defense informing offense as a rationale for portfolio integration.",
        "url": "https://cpeisw.army.mil/2026/08/03/constant-modernization-the-establishment-of-project-manager-cyber-warfare/"
      },
      {
        "section": "Portfolio integration",
        "sourceId": "SRC-USAASC-CYBER-WARFARE-2026",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The Army describes integrated offensive and defensive cyber portfolios and rapid collaboration with commercial technology partners.",
        "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/"
      },
      {
        "section": "Conclusion",
        "sourceId": "SRC-USAASC-CYBER-WARFARE-2026",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The article frames cyber capability as both defending critical infrastructure and enabling approved cyber operations.",
        "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/threat-emulation-vs-live-offensive-operation/#clm-k04-cmp-037",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K04 STRATEGIC RECORD",
    "id": "CLM-K04-CMP-037",
    "lastReviewed": "2026-08-15",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-cmp-037.json",
    "name": "Threat Emulation versus Live Offensive Operation",
    "ownerAnchor": "clm-k04-cmp-037",
    "ownerId": "K04-CMP-037",
    "ownerRoute": "/comparisons/threat-emulation-vs-live-offensive-operation/",
    "ownerType": "comparison",
    "proposition": "Threat emulation reproduces selected behaviors in an authorized controlled environment; a live offensive operation affects external target systems under mission authority.",
    "qualification": "The matrix prevents category error but does not determine every facility, mission, target, jurisdiction, or operational case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-15",
    "scope": "Canonical K04 distinction between Threat Emulation and Live Offensive Operation.",
    "slug": "clm-k04-cmp-037",
    "sourceIds": [
      "SRC-DODD-3000-09",
      "SRC-INL-CCE",
      "SRC-NIST-800-82R3"
    ],
    "sourceSections": [
      {
        "section": "Policy 1.2(a)-(b)",
        "sourceId": "SRC-DODD-3000-09",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Autonomous and semi-autonomous weapon systems must allow appropriate human judgment over force and undergo rigorous verification, validation, testing, cybersecurity, and lawful use.",
        "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF"
      },
      {
        "section": "Responsibilities and testing",
        "sourceId": "SRC-DODD-3000-09",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The directive assigns approval, legal review, test, monitoring, operator understanding, abort, and post-fielding responsibilities.",
        "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF"
      },
      {
        "section": "CCE methodology",
        "sourceId": "SRC-INL-CCE",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.",
        "url": "https://inl.gov/national-security/cce/"
      },
      {
        "section": "Critical function focus",
        "sourceId": "SRC-INL-CCE",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "CCE evaluates what must be safeguarded and applies engineering strategies to isolate and protect critical assets and functions.",
        "url": "https://inl.gov/feature-story/consequence-driven-cyber-informed-engineering-the-rise-of-a-national-security-pillar/"
      },
      {
        "section": "Abstract",
        "sourceId": "SRC-NIST-800-82R3",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.",
        "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/simulation-readiness-vs-operational-readiness/#clm-k04-cmp-038",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K04 STRATEGIC RECORD",
    "id": "CLM-K04-CMP-038",
    "lastReviewed": "2026-08-15",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-cmp-038.json",
    "name": "Simulation Readiness versus Operational Readiness",
    "ownerAnchor": "clm-k04-cmp-038",
    "ownerId": "K04-CMP-038",
    "ownerRoute": "/comparisons/simulation-readiness-vs-operational-readiness/",
    "ownerType": "comparison",
    "proposition": "Simulation readiness shows bounded performance in a test model; operational readiness requires deployment, environment-specific verification, sustainment, authority, and current operating evidence.",
    "qualification": "The matrix prevents category error but does not determine every facility, mission, target, jurisdiction, or operational case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-15",
    "scope": "Canonical K04 distinction between Simulation Readiness and Operational Readiness.",
    "slug": "clm-k04-cmp-038",
    "sourceIds": [
      "SRC-DODD-3000-09",
      "SRC-INL-CCE",
      "SRC-NIST-800-82R3"
    ],
    "sourceSections": [
      {
        "section": "Policy 1.2(a)-(b)",
        "sourceId": "SRC-DODD-3000-09",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Autonomous and semi-autonomous weapon systems must allow appropriate human judgment over force and undergo rigorous verification, validation, testing, cybersecurity, and lawful use.",
        "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF"
      },
      {
        "section": "Responsibilities and testing",
        "sourceId": "SRC-DODD-3000-09",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The directive assigns approval, legal review, test, monitoring, operator understanding, abort, and post-fielding responsibilities.",
        "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF"
      },
      {
        "section": "CCE methodology",
        "sourceId": "SRC-INL-CCE",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.",
        "url": "https://inl.gov/national-security/cce/"
      },
      {
        "section": "Critical function focus",
        "sourceId": "SRC-INL-CCE",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "CCE evaluates what must be safeguarded and applies engineering strategies to isolate and protect critical assets and functions.",
        "url": "https://inl.gov/feature-story/consequence-driven-cyber-informed-engineering-the-rise-of-a-national-security-pillar/"
      },
      {
        "section": "Abstract",
        "sourceId": "SRC-NIST-800-82R3",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.",
        "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/mission-command-autonomy-vs-self-authorized-action/#clm-k04-cmp-039",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K04 STRATEGIC RECORD",
    "id": "CLM-K04-CMP-039",
    "lastReviewed": "2026-08-15",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-cmp-039.json",
    "name": "Mission-Command Autonomy versus Self-Authorized Action",
    "ownerAnchor": "clm-k04-cmp-039",
    "ownerId": "K04-CMP-039",
    "ownerRoute": "/comparisons/mission-command-autonomy-vs-self-authorized-action/",
    "ownerType": "comparison",
    "proposition": "Mission-command autonomy executes assigned intent within delegated limits when disconnected; self-authorized action creates a new mission, target, or effect without authority.",
    "qualification": "The matrix prevents category error but does not determine every facility, mission, target, jurisdiction, or operational case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-15",
    "scope": "Canonical K04 distinction between Mission-Command Autonomy and Self-Authorized Action.",
    "slug": "clm-k04-cmp-039",
    "sourceIds": [
      "SRC-DODD-3000-09",
      "SRC-USAASC-PM-CW-2026",
      "SRC-USAASC-CYBER-WARFARE-2026"
    ],
    "sourceSections": [
      {
        "section": "Policy 1.2(a)-(b)",
        "sourceId": "SRC-DODD-3000-09",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Autonomous and semi-autonomous weapon systems must allow appropriate human judgment over force and undergo rigorous verification, validation, testing, cybersecurity, and lawful use.",
        "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF"
      },
      {
        "section": "Responsibilities and testing",
        "sourceId": "SRC-DODD-3000-09",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The directive assigns approval, legal review, test, monitoring, operator understanding, abort, and post-fielding responsibilities.",
        "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF"
      },
      {
        "section": "Establishment and mission",
        "sourceId": "SRC-USAASC-PM-CW-2026",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Project Manager Cyber Warfare was formed from the merger of PM Defensive Cyber Operations and PM Cyber and Space to deliver integrated cyber capabilities.",
        "url": "https://cpeisw.army.mil/2026/08/03/constant-modernization-the-establishment-of-project-manager-cyber-warfare/"
      },
      {
        "section": "Offense-defense feedback",
        "sourceId": "SRC-USAASC-PM-CW-2026",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The official statement presents offense informing defense and defense informing offense as a rationale for portfolio integration.",
        "url": "https://cpeisw.army.mil/2026/08/03/constant-modernization-the-establishment-of-project-manager-cyber-warfare/"
      },
      {
        "section": "Portfolio integration",
        "sourceId": "SRC-USAASC-CYBER-WARFARE-2026",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The Army describes integrated offensive and defensive cyber portfolios and rapid collaboration with commercial technology partners.",
        "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/"
      },
      {
        "section": "Conclusion",
        "sourceId": "SRC-USAASC-CYBER-WARFARE-2026",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The article frames cyber capability as both defending critical infrastructure and enabling approved cyber operations.",
        "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/defense-supremacy-vs-offense-dominance/#clm-k04-cmp-040",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K04 STRATEGIC RECORD",
    "id": "CLM-K04-CMP-040",
    "lastReviewed": "2026-08-15",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-cmp-040.json",
    "name": "Deterrence by Denial versus Offense Dominance",
    "ownerAnchor": "clm-k04-cmp-040",
    "ownerId": "K04-CMP-040",
    "ownerRoute": "/comparisons/defense-supremacy-vs-offense-dominance/",
    "ownerType": "comparison",
    "proposition": "Deterrence by denial raises adversary cost through resilience and recovery; offense dominance assumes access and exploitation create lasting strategic advantage.",
    "qualification": "The matrix prevents category error but does not determine every facility, mission, target, jurisdiction, or operational case.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-15",
    "scope": "Canonical K04 distinction between Deterrence by Denial and Offense Dominance.",
    "slug": "clm-k04-cmp-040",
    "sourceIds": [
      "SRC-INL-CCE",
      "SRC-NIST-800-82R3",
      "SRC-NIST-800-207",
      "SRC-NRC-10CFR-73-54"
    ],
    "sourceSections": [
      {
        "section": "CCE methodology",
        "sourceId": "SRC-INL-CCE",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.",
        "url": "https://inl.gov/national-security/cce/"
      },
      {
        "section": "Critical function focus",
        "sourceId": "SRC-INL-CCE",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "CCE evaluates what must be safeguarded and applies engineering strategies to isolate and protect critical assets and functions.",
        "url": "https://inl.gov/feature-story/consequence-driven-cyber-informed-engineering-the-rise-of-a-national-security-pillar/"
      },
      {
        "section": "Abstract",
        "sourceId": "SRC-NIST-800-82R3",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.",
        "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final"
      },
      {
        "section": "Abstract",
        "sourceId": "SRC-NIST-800-207",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Zero trust shifts protection away from static network perimeters, assumes no implicit trust by location or ownership, and requires discrete authentication and authorization.",
        "url": "https://csrc.nist.gov/pubs/sp/800/207/final"
      },
      {
        "section": "73.54(a)",
        "sourceId": "SRC-NRC-10CFR-73-54",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.",
        "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54"
      },
      {
        "section": "73.54(b)",
        "sourceId": "SRC-NRC-10CFR-73-54",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The regulation requires asset analysis and an implemented and maintained cybersecurity program for protected assets.",
        "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/control-mapping-vs-compliance-determination/#clm-k05-cmp-001",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K05 RECORD",
    "id": "CLM-K05-CMP-001",
    "lastReviewed": "2026-08-15",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k05-cmp-001.json",
    "name": "Control Mapping versus Compliance Determination",
    "ownerAnchor": "clm-k05-cmp-001",
    "ownerId": "K05-CMP-001",
    "ownerRoute": "/comparisons/control-mapping-vs-compliance-determination/",
    "ownerType": "comparison",
    "proposition": "A mapping records relevance and applicability hypotheses; a compliance determination requires the governing authority, facility scope, implementation evidence, exceptions, and authorized judgment.",
    "qualification": "The distinction prevents category error but does not substitute for a site-, mission-, authority-, or jurisdiction-specific determination.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-15",
    "scope": "K05 canonical distinction between Control Mapping and Compliance Determination.",
    "slug": "clm-k05-cmp-001",
    "sourceIds": [
      "SRC-NIST-800-82R3",
      "SRC-NIST-800-207",
      "SRC-NRC-10CFR-73-SUBPART-J-2026",
      "SRC-NERC-CIP-CATALOG-2026"
    ],
    "sourceSections": [
      {
        "section": "Abstract",
        "sourceId": "SRC-NIST-800-82R3",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.",
        "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final"
      },
      {
        "section": "Abstract",
        "sourceId": "SRC-NIST-800-207",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Zero trust shifts protection away from static network perimeters, assumes no implicit trust by location or ownership, and requires discrete authentication and authorization.",
        "url": "https://csrc.nist.gov/pubs/sp/800/207/final"
      },
      {
        "section": "73.100",
        "sourceId": "SRC-NRC-10CFR-73-SUBPART-J-2026",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Technology-inclusive physical-protection requirements are available for qualifying Part 53 licensees that elect the section.",
        "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.100"
      },
      {
        "section": "73.110",
        "sourceId": "SRC-NRC-10CFR-73-SUBPART-J-2026",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Technology-inclusive protection requirements address covered digital computer and communication systems and networks.",
        "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.110"
      },
      {
        "section": "73.120",
        "sourceId": "SRC-NRC-10CFR-73-SUBPART-J-2026",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The Subpart J framework includes an access-authorization program for covered commercial nuclear plants.",
        "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.120"
      },
      {
        "section": "CIP standards catalog",
        "sourceId": "SRC-NERC-CIP-CATALOG-2026",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "NERC maintains the official catalog of CIP reliability standards; exact obligations require the current standard text and a facility-specific applicability analysis.",
        "url": "https://www.nerc.com/standards/reliability-standards/cip"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/assurance-claim-vs-marketing-claim/#clm-k05-cmp-002",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K05 RECORD",
    "id": "CLM-K05-CMP-002",
    "lastReviewed": "2026-08-15",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k05-cmp-002.json",
    "name": "Assurance Claim versus Marketing Claim",
    "ownerAnchor": "clm-k05-cmp-002",
    "ownerId": "K05-CMP-002",
    "ownerRoute": "/comparisons/assurance-claim-vs-marketing-claim/",
    "ownerType": "comparison",
    "proposition": "An assurance claim exposes evidence, assumptions, defeaters, hazards, and failure conditions; a marketing claim primarily seeks persuasion and may omit what would falsify it.",
    "qualification": "The distinction prevents category error but does not substitute for a site-, mission-, authority-, or jurisdiction-specific determination.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-15",
    "scope": "K05 canonical distinction between Assurance Claim and Marketing Claim.",
    "slug": "clm-k05-cmp-002",
    "sourceIds": [
      "SRC-INL-CCE",
      "SRC-NIST-800-82R3",
      "SRC-NRC-10CFR-73-54"
    ],
    "sourceSections": [
      {
        "section": "CCE methodology",
        "sourceId": "SRC-INL-CCE",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.",
        "url": "https://inl.gov/national-security/cce/"
      },
      {
        "section": "Critical function focus",
        "sourceId": "SRC-INL-CCE",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "CCE evaluates what must be safeguarded and applies engineering strategies to isolate and protect critical assets and functions.",
        "url": "https://inl.gov/feature-story/consequence-driven-cyber-informed-engineering-the-rise-of-a-national-security-pillar/"
      },
      {
        "section": "Abstract",
        "sourceId": "SRC-NIST-800-82R3",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.",
        "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final"
      },
      {
        "section": "73.54(a)",
        "sourceId": "SRC-NRC-10CFR-73-54",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.",
        "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54"
      },
      {
        "section": "73.54(b)",
        "sourceId": "SRC-NRC-10CFR-73-54",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The regulation requires asset analysis and an implemented and maintained cybersecurity program for protected assets.",
        "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/range-result-vs-field-performance/#clm-k05-cmp-003",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K05 RECORD",
    "id": "CLM-K05-CMP-003",
    "lastReviewed": "2026-08-15",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k05-cmp-003.json",
    "name": "Evaluation Range Result versus Field Performance",
    "ownerAnchor": "clm-k05-cmp-003",
    "ownerId": "K05-CMP-003",
    "ownerRoute": "/comparisons/range-result-vs-field-performance/",
    "ownerType": "comparison",
    "proposition": "A range result supports a bounded test proposition under declared conditions; field performance requires deployment identity, environment, sustainment, incidents, uptime, and current operational evidence.",
    "qualification": "The distinction prevents category error but does not substitute for a site-, mission-, authority-, or jurisdiction-specific determination.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-15",
    "scope": "K05 canonical distinction between Evaluation Range Result and Field Performance.",
    "slug": "clm-k05-cmp-003",
    "sourceIds": [
      "SRC-DODD-3000-09",
      "SRC-INL-CCE",
      "SRC-NIST-800-82R3"
    ],
    "sourceSections": [
      {
        "section": "Section 1.1(a)-(b) — Applicability and exclusions",
        "sourceId": "SRC-DODD-3000-09",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The directive applies to autonomous and semi-autonomous weapon systems and expressly excludes autonomous or semi-autonomous cyberspace capabilities and systems that are not weapon systems.",
        "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF"
      },
      {
        "section": "Section 1.2(a) — Weapon-system policy",
        "sourceId": "SRC-DODD-3000-09",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Within its weapon-system scope, the directive requires appropriate human judgment, rigorous verification and validation, realistic test and evaluation, robustness, transparency, auditability, and bounded engagement behavior.",
        "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF"
      },
      {
        "section": "CCE methodology",
        "sourceId": "SRC-INL-CCE",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.",
        "url": "https://inl.gov/national-security/cce/"
      },
      {
        "section": "Critical function focus",
        "sourceId": "SRC-INL-CCE",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "CCE evaluates what must be safeguarded and applies engineering strategies to isolate and protect critical assets and functions.",
        "url": "https://inl.gov/feature-story/consequence-driven-cyber-informed-engineering-the-rise-of-a-national-security-pillar/"
      },
      {
        "section": "Abstract",
        "sourceId": "SRC-NIST-800-82R3",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.",
        "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/source-revalidation-vs-running-monitoring/#clm-k05-cmp-004",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K05 RECORD",
    "id": "CLM-K05-CMP-004",
    "lastReviewed": "2026-08-15",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k05-cmp-004.json",
    "name": "Point-in-Time Revalidation versus Running Monitoring",
    "ownerAnchor": "clm-k05-cmp-004",
    "ownerId": "K05-CMP-004",
    "ownerRoute": "/comparisons/source-revalidation-vs-running-monitoring/",
    "ownerType": "comparison",
    "proposition": "Revalidation records what an official source said at a declared time; running monitoring requires an operating service, observation cadence, failure handling, and current heartbeat evidence.",
    "qualification": "The distinction prevents category error but does not substitute for a site-, mission-, authority-, or jurisdiction-specific determination.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-15",
    "scope": "K05 canonical distinction between Point-in-Time Revalidation and Running Monitoring.",
    "slug": "clm-k05-cmp-004",
    "sourceIds": [
      "SRC-W3C-PROV-O"
    ],
    "sourceSections": [
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "PROV-O at a glance",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.",
        "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/uas-restriction-vs-counter-uas-mitigation-authority/#clm-k05-cmp-005",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K05 RECORD",
    "id": "CLM-K05-CMP-005",
    "lastReviewed": "2026-08-15",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k05-cmp-005.json",
    "name": "Airspace Restriction versus Counter-UAS Mitigation Authority",
    "ownerAnchor": "clm-k05-cmp-005",
    "ownerId": "K05-CMP-005",
    "ownerRoute": "/comparisons/uas-restriction-vs-counter-uas-mitigation-authority/",
    "ownerType": "comparison",
    "proposition": "A restriction defines prohibited or controlled flight behavior; mitigation authority separately governs interception, interference, seizure, disabling, or destruction and is actor- and statute-specific.",
    "qualification": "The distinction prevents category error but does not substitute for a site-, mission-, authority-, or jurisdiction-specific determination.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-15",
    "scope": "K05 canonical distinction between Airspace Restriction and Counter-UAS Mitigation Authority.",
    "slug": "clm-k05-cmp-005",
    "sourceIds": [
      "SRC-FAA-CI-UAS-NPRM-2026",
      "SRC-USC-6-124N",
      "SRC-USC-47-333"
    ],
    "sourceSections": [
      {
        "section": "Proposed petition process",
        "sourceId": "SRC-FAA-CI-UAS-NPRM-2026",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The FAA proposed a process for operators of certain critical-infrastructure sites to petition for restrictions on drone operations over those sites.",
        "url": "https://www.faa.gov/newsroom/restricting-drones-near-critical-infrastructure-sites"
      },
      {
        "section": "Authorities and covered facilities",
        "sourceId": "SRC-USC-6-124N",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "The statute assigns specified counter-UAS authorities and constraints to federal departments for covered facilities and missions.",
        "url": "https://uscode.house.gov/view.xhtml?req=%28title%3A6+section%3A124n+edition%3Aprelim%29"
      },
      {
        "section": "Section 333 prohibition",
        "sourceId": "SRC-USC-47-333",
        "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
        "supports": "No person may willfully or maliciously interfere with authorized radio communications, absent a separate applicable authority or exception.",
        "url": "https://uscode.house.gov/view.xhtml?req=%28title%3A47+section%3A333+edition%3Aprelim%29"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/facility-pattern-vs-final-design/#clm-k07-cmp-001",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-001",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-001.json",
    "name": "Facility pattern versus Final design",
    "ownerAnchor": "clm-k07-cmp-001",
    "ownerId": "K07-CMP-001",
    "ownerRoute": "/comparisons/facility-pattern-vs-final-design/",
    "ownerType": "comparison",
    "proposition": "Facility pattern and Final design answer different questions and must not be collapsed.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Facility pattern and Final design.",
    "slug": "clm-k07-cmp-001",
    "sourceIds": [
      "SRC-W3C-PROV-O",
      "SRC-RFC-3161",
      "SRC-C2PA",
      "SRC-IN-TOTO"
    ],
    "sourceSections": [
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "RFC status and update chain",
        "sourceId": "SRC-RFC-3161",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.",
        "url": "https://www.rfc-editor.org/info/rfc3161/"
      },
      {
        "section": "Version history — 2.4",
        "sourceId": "SRC-C2PA",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.",
        "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/currentness-import-vs-live-monitoring/#clm-k07-cmp-002",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-002",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-002.json",
    "name": "Offline currentness import versus Live monitoring",
    "ownerAnchor": "clm-k07-cmp-002",
    "ownerId": "K07-CMP-002",
    "ownerRoute": "/comparisons/currentness-import-vs-live-monitoring/",
    "ownerType": "comparison",
    "proposition": "Offline currentness import and Live monitoring answer different questions and must not be collapsed.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Offline currentness import and Live monitoring.",
    "slug": "clm-k07-cmp-002",
    "sourceIds": [
      "SRC-W3C-PROV-O",
      "SRC-RFC-3161",
      "SRC-C2PA",
      "SRC-IN-TOTO"
    ],
    "sourceSections": [
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "RFC status and update chain",
        "sourceId": "SRC-RFC-3161",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.",
        "url": "https://www.rfc-editor.org/info/rfc3161/"
      },
      {
        "section": "Version history — 2.4",
        "sourceId": "SRC-C2PA",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.",
        "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/red-team-evidence-vs-exploit-disclosure/#clm-k07-cmp-003",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-003",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-003.json",
    "name": "Red-team evidence versus Exploit disclosure",
    "ownerAnchor": "clm-k07-cmp-003",
    "ownerId": "K07-CMP-003",
    "ownerRoute": "/comparisons/red-team-evidence-vs-exploit-disclosure/",
    "ownerType": "comparison",
    "proposition": "Red-team evidence and Exploit disclosure answer different questions and must not be collapsed.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Red-team evidence and Exploit disclosure.",
    "slug": "clm-k07-cmp-003",
    "sourceIds": [
      "SRC-W3C-PROV-O",
      "SRC-RFC-3161",
      "SRC-C2PA",
      "SRC-IN-TOTO"
    ],
    "sourceSections": [
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "RFC status and update chain",
        "sourceId": "SRC-RFC-3161",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.",
        "url": "https://www.rfc-editor.org/info/rfc3161/"
      },
      {
        "section": "Version history — 2.4",
        "sourceId": "SRC-C2PA",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.",
        "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/procurement-work-package-vs-capability-claim/#clm-k07-cmp-004",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-004",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-004.json",
    "name": "Procurement work package versus Capability claim",
    "ownerAnchor": "clm-k07-cmp-004",
    "ownerId": "K07-CMP-004",
    "ownerRoute": "/comparisons/procurement-work-package-vs-capability-claim/",
    "ownerType": "comparison",
    "proposition": "Procurement work package and Capability claim answer different questions and must not be collapsed.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Procurement work package and Capability claim.",
    "slug": "clm-k07-cmp-004",
    "sourceIds": [
      "SRC-W3C-PROV-O",
      "SRC-RFC-3161",
      "SRC-C2PA",
      "SRC-IN-TOTO"
    ],
    "sourceSections": [
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "RFC status and update chain",
        "sourceId": "SRC-RFC-3161",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.",
        "url": "https://www.rfc-editor.org/info/rfc3161/"
      },
      {
        "section": "Version history — 2.4",
        "sourceId": "SRC-C2PA",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.",
        "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/mapping-quality-vs-compliance-status/#clm-k07-cmp-005",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-005",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-005.json",
    "name": "Mapping quality versus Compliance status",
    "ownerAnchor": "clm-k07-cmp-005",
    "ownerId": "K07-CMP-005",
    "ownerRoute": "/comparisons/mapping-quality-vs-compliance-status/",
    "ownerType": "comparison",
    "proposition": "Mapping quality and Compliance status answer different questions and must not be collapsed.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Mapping quality and Compliance status.",
    "slug": "clm-k07-cmp-005",
    "sourceIds": [
      "SRC-W3C-PROV-O",
      "SRC-RFC-3161",
      "SRC-C2PA",
      "SRC-IN-TOTO"
    ],
    "sourceSections": [
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "RFC status and update chain",
        "sourceId": "SRC-RFC-3161",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.",
        "url": "https://www.rfc-editor.org/info/rfc3161/"
      },
      {
        "section": "Version history — 2.4",
        "sourceId": "SRC-C2PA",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.",
        "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/generic-pattern-vs-site-evidence-bundle/#clm-k07-cmp-006",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-006",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-006.json",
    "name": "Generic facility pattern versus Site evidence bundle",
    "ownerAnchor": "clm-k07-cmp-006",
    "ownerId": "K07-CMP-006",
    "ownerRoute": "/comparisons/generic-pattern-vs-site-evidence-bundle/",
    "ownerType": "comparison",
    "proposition": "Generic facility pattern and Site evidence bundle answer different evidentiary and decision questions and must not be collapsed.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Generic facility pattern and Site evidence bundle.",
    "slug": "clm-k07-cmp-006",
    "sourceIds": [
      "SRC-W3C-PROV-O",
      "SRC-RFC-3161",
      "SRC-C2PA",
      "SRC-IN-TOTO"
    ],
    "sourceSections": [
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "RFC status and update chain",
        "sourceId": "SRC-RFC-3161",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.",
        "url": "https://www.rfc-editor.org/info/rfc3161/"
      },
      {
        "section": "Version history — 2.4",
        "sourceId": "SRC-C2PA",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.",
        "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/bill-of-materials-vs-security-assurance/#clm-k07-cmp-007",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-007",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-007.json",
    "name": "Bill of materials versus Security assurance",
    "ownerAnchor": "clm-k07-cmp-007",
    "ownerId": "K07-CMP-007",
    "ownerRoute": "/comparisons/bill-of-materials-vs-security-assurance/",
    "ownerType": "comparison",
    "proposition": "Bill of materials and Security assurance answer different evidentiary and decision questions and must not be collapsed.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Bill of materials and Security assurance.",
    "slug": "clm-k07-cmp-007",
    "sourceIds": [
      "SRC-W3C-PROV-O",
      "SRC-RFC-3161",
      "SRC-C2PA",
      "SRC-IN-TOTO"
    ],
    "sourceSections": [
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "RFC status and update chain",
        "sourceId": "SRC-RFC-3161",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.",
        "url": "https://www.rfc-editor.org/info/rfc3161/"
      },
      {
        "section": "Version history — 2.4",
        "sourceId": "SRC-C2PA",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.",
        "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/signed-receipt-vs-factual-truth/#clm-k07-cmp-008",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-008",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-008.json",
    "name": "Signed evidence receipt versus Factual truth",
    "ownerAnchor": "clm-k07-cmp-008",
    "ownerId": "K07-CMP-008",
    "ownerRoute": "/comparisons/signed-receipt-vs-factual-truth/",
    "ownerType": "comparison",
    "proposition": "Signed evidence receipt and Factual truth answer different evidentiary and decision questions and must not be collapsed.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Signed evidence receipt and Factual truth.",
    "slug": "clm-k07-cmp-008",
    "sourceIds": [
      "SRC-W3C-PROV-O",
      "SRC-RFC-3161",
      "SRC-C2PA",
      "SRC-IN-TOTO"
    ],
    "sourceSections": [
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "RFC status and update chain",
        "sourceId": "SRC-RFC-3161",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.",
        "url": "https://www.rfc-editor.org/info/rfc3161/"
      },
      {
        "section": "Version history — 2.4",
        "sourceId": "SRC-C2PA",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.",
        "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/digital-twin-vs-live-facility/#clm-k07-cmp-009",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-009",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-009.json",
    "name": "Digital twin versus Live facility",
    "ownerAnchor": "clm-k07-cmp-009",
    "ownerId": "K07-CMP-009",
    "ownerRoute": "/comparisons/digital-twin-vs-live-facility/",
    "ownerType": "comparison",
    "proposition": "Digital twin and Live facility answer different evidentiary and decision questions and must not be collapsed.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Digital twin and Live facility.",
    "slug": "clm-k07-cmp-009",
    "sourceIds": [
      "SRC-W3C-PROV-O",
      "SRC-RFC-3161",
      "SRC-C2PA",
      "SRC-IN-TOTO"
    ],
    "sourceSections": [
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "RFC status and update chain",
        "sourceId": "SRC-RFC-3161",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.",
        "url": "https://www.rfc-editor.org/info/rfc3161/"
      },
      {
        "section": "Version history — 2.4",
        "sourceId": "SRC-C2PA",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.",
        "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/performance-standard-vs-prescribed-method/#clm-k07-cmp-010",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-010",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-010.json",
    "name": "Performance standard versus Prescribed method",
    "ownerAnchor": "clm-k07-cmp-010",
    "ownerId": "K07-CMP-010",
    "ownerRoute": "/comparisons/performance-standard-vs-prescribed-method/",
    "ownerType": "comparison",
    "proposition": "Performance standard and Prescribed method answer different evidentiary and decision questions and must not be collapsed.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Performance standard and Prescribed method.",
    "slug": "clm-k07-cmp-010",
    "sourceIds": [
      "SRC-W3C-PROV-O",
      "SRC-RFC-3161",
      "SRC-C2PA",
      "SRC-IN-TOTO"
    ],
    "sourceSections": [
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "RFC status and update chain",
        "sourceId": "SRC-RFC-3161",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.",
        "url": "https://www.rfc-editor.org/info/rfc3161/"
      },
      {
        "section": "Version history — 2.4",
        "sourceId": "SRC-C2PA",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.",
        "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/runic-token-vs-cryptographic-token/#clm-k07-cmp-011",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-011",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-011.json",
    "name": "Runic protocol token versus Cryptographic token",
    "ownerAnchor": "clm-k07-cmp-011",
    "ownerId": "K07-CMP-011",
    "ownerRoute": "/comparisons/runic-token-vs-cryptographic-token/",
    "ownerType": "comparison",
    "proposition": "Runic protocol token and Cryptographic token answer different technical or evidentiary questions and must not be collapsed.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Runic protocol token and Cryptographic token.",
    "slug": "clm-k07-cmp-011",
    "sourceIds": [
      "SRC-UNICODE-RUNIC-17",
      "SRC-UNICODE-UAX15-17",
      "SRC-RFC-5646",
      "SRC-W3C-PROV-O"
    ],
    "sourceSections": [
      {
        "section": "Runic range and character names",
        "sourceId": "SRC-UNICODE-RUNIC-17",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.",
        "url": "https://www.unicode.org/charts/PDF/U16A0.pdf"
      },
      {
        "section": "Normalization forms and conformance",
        "sourceId": "SRC-UNICODE-UAX15-17",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.",
        "url": "https://www.unicode.org/reports/tr15/"
      },
      {
        "section": "Language-tag structure and semantics",
        "sourceId": "SRC-RFC-5646",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Language tags identify the language and optional script or region of an information object.",
        "url": "https://www.rfc-editor.org/rfc/rfc5646"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/u-label-vs-a-label/#clm-k07-cmp-012",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-012",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-012.json",
    "name": "U-label versus A-label",
    "ownerAnchor": "clm-k07-cmp-012",
    "ownerId": "K07-CMP-012",
    "ownerRoute": "/comparisons/u-label-vs-a-label/",
    "ownerType": "comparison",
    "proposition": "U-label and A-label answer different technical or evidentiary questions and must not be collapsed.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between U-label and A-label.",
    "slug": "clm-k07-cmp-012",
    "sourceIds": [
      "SRC-UNICODE-RUNIC-17",
      "SRC-UNICODE-UAX15-17",
      "SRC-RFC-3492",
      "SRC-RFC-5890",
      "SRC-RFC-5891"
    ],
    "sourceSections": [
      {
        "section": "Runic range and character names",
        "sourceId": "SRC-UNICODE-RUNIC-17",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.",
        "url": "https://www.unicode.org/charts/PDF/U16A0.pdf"
      },
      {
        "section": "Normalization forms and conformance",
        "sourceId": "SRC-UNICODE-UAX15-17",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.",
        "url": "https://www.unicode.org/reports/tr15/"
      },
      {
        "section": "Abstract and encoding algorithm",
        "sourceId": "SRC-RFC-3492",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Punycode reversibly encodes Unicode strings into a restricted ASCII form for IDNA use.",
        "url": "https://www.rfc-editor.org/rfc/rfc3492"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/symbolic-compression-vs-semantic-preservation/#clm-k07-cmp-013",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-013",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-013.json",
    "name": "Symbolic compression versus Semantic preservation",
    "ownerAnchor": "clm-k07-cmp-013",
    "ownerId": "K07-CMP-013",
    "ownerRoute": "/comparisons/symbolic-compression-vs-semantic-preservation/",
    "ownerType": "comparison",
    "proposition": "Symbolic compression and Semantic preservation answer different technical or evidentiary questions and must not be collapsed.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Symbolic compression and Semantic preservation.",
    "slug": "clm-k07-cmp-013",
    "sourceIds": [
      "SRC-UNICODE-RUNIC-17",
      "SRC-UNICODE-UAX15-17",
      "SRC-RFC-5646",
      "SRC-W3C-PROV-O"
    ],
    "sourceSections": [
      {
        "section": "Runic range and character names",
        "sourceId": "SRC-UNICODE-RUNIC-17",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.",
        "url": "https://www.unicode.org/charts/PDF/U16A0.pdf"
      },
      {
        "section": "Normalization forms and conformance",
        "sourceId": "SRC-UNICODE-UAX15-17",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.",
        "url": "https://www.unicode.org/reports/tr15/"
      },
      {
        "section": "Language-tag structure and semantics",
        "sourceId": "SRC-RFC-5646",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Language tags identify the language and optional script or region of an information object.",
        "url": "https://www.rfc-editor.org/rfc/rfc5646"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/range-success-vs-field-readiness/#clm-k07-cmp-014",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-014",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-014.json",
    "name": "Range success versus Field readiness",
    "ownerAnchor": "clm-k07-cmp-014",
    "ownerId": "K07-CMP-014",
    "ownerRoute": "/comparisons/range-success-vs-field-readiness/",
    "ownerType": "comparison",
    "proposition": "Range success and Field readiness answer different technical or evidentiary questions and must not be collapsed.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Range success and Field readiness.",
    "slug": "clm-k07-cmp-014",
    "sourceIds": [
      "SRC-DODD-3000-09",
      "SRC-INL-CCE",
      "SRC-NIST-800-82R3"
    ],
    "sourceSections": [
      {
        "section": "Section 1.1(a)-(b) — Applicability and exclusions",
        "sourceId": "SRC-DODD-3000-09",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "The directive applies to autonomous and semi-autonomous weapon systems and expressly excludes autonomous or semi-autonomous cyberspace capabilities and systems that are not weapon systems.",
        "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF"
      },
      {
        "section": "CCE methodology",
        "sourceId": "SRC-INL-CCE",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.",
        "url": "https://inl.gov/national-security/cce/"
      },
      {
        "section": "Abstract",
        "sourceId": "SRC-NIST-800-82R3",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.",
        "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/trace-completeness-vs-claim-satisfaction/#clm-k07-cmp-015",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-015",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-015.json",
    "name": "Trace completeness versus Claim satisfaction",
    "ownerAnchor": "clm-k07-cmp-015",
    "ownerId": "K07-CMP-015",
    "ownerRoute": "/comparisons/trace-completeness-vs-claim-satisfaction/",
    "ownerType": "comparison",
    "proposition": "Trace completeness and Claim satisfaction answer different technical or evidentiary questions and must not be collapsed.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Trace completeness and Claim satisfaction.",
    "slug": "clm-k07-cmp-015",
    "sourceIds": [
      "SRC-W3C-PROV-O",
      "SRC-RFC-3161",
      "SRC-C2PA",
      "SRC-IN-TOTO"
    ],
    "sourceSections": [
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "RFC status and update chain",
        "sourceId": "SRC-RFC-3161",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.",
        "url": "https://www.rfc-editor.org/info/rfc3161/"
      },
      {
        "section": "Version history — 2.4",
        "sourceId": "SRC-C2PA",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.",
        "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/conformance-vs-security/#clm-k07-cmp-016",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-016",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-016.json",
    "name": "Protocol conformance versus Operational security",
    "ownerAnchor": "clm-k07-cmp-016",
    "ownerId": "K07-CMP-016",
    "ownerRoute": "/comparisons/conformance-vs-security/",
    "ownerType": "comparison",
    "proposition": "Protocol conformance and Operational security answer different evidentiary or operational questions and must remain separate.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Protocol conformance and Operational security.",
    "slug": "clm-k07-cmp-016",
    "sourceIds": [
      "SRC-UNICODE-RUNIC-17",
      "SRC-UNICODE-UAX15-17",
      "SRC-RFC-5646",
      "SRC-W3C-PROV-O"
    ],
    "sourceSections": [
      {
        "section": "Runic range and character names",
        "sourceId": "SRC-UNICODE-RUNIC-17",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.",
        "url": "https://www.unicode.org/charts/PDF/U16A0.pdf"
      },
      {
        "section": "Normalization forms and conformance",
        "sourceId": "SRC-UNICODE-UAX15-17",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.",
        "url": "https://www.unicode.org/reports/tr15/"
      },
      {
        "section": "Language-tag structure and semantics",
        "sourceId": "SRC-RFC-5646",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Language tags identify the language and optional script or region of an information object.",
        "url": "https://www.rfc-editor.org/rfc/rfc5646"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/unicode-validity-vs-hosting/#clm-k07-cmp-017",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-017",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-017.json",
    "name": "Unicode/IDNA validity versus Observed hosting",
    "ownerAnchor": "clm-k07-cmp-017",
    "ownerId": "K07-CMP-017",
    "ownerRoute": "/comparisons/unicode-validity-vs-hosting/",
    "ownerType": "comparison",
    "proposition": "Unicode/IDNA validity and Observed hosting answer different evidentiary or operational questions and must remain separate.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Unicode/IDNA validity and Observed hosting.",
    "slug": "clm-k07-cmp-017",
    "sourceIds": [
      "SRC-UNICODE-RUNIC-17",
      "SRC-UNICODE-UAX15-17",
      "SRC-RFC-3492",
      "SRC-RFC-5890",
      "SRC-RFC-5891"
    ],
    "sourceSections": [
      {
        "section": "Runic range and character names",
        "sourceId": "SRC-UNICODE-RUNIC-17",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.",
        "url": "https://www.unicode.org/charts/PDF/U16A0.pdf"
      },
      {
        "section": "Normalization forms and conformance",
        "sourceId": "SRC-UNICODE-UAX15-17",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.",
        "url": "https://www.unicode.org/reports/tr15/"
      },
      {
        "section": "Abstract and encoding algorithm",
        "sourceId": "SRC-RFC-3492",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Punycode reversibly encodes Unicode strings into a restricted ASCII form for IDNA use.",
        "url": "https://www.rfc-editor.org/rfc/rfc3492"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/source-event-vs-verified-event/#clm-k07-cmp-018",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-018",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-018.json",
    "name": "Source-derived event versus Independently verified event",
    "ownerAnchor": "clm-k07-cmp-018",
    "ownerId": "K07-CMP-018",
    "ownerRoute": "/comparisons/source-event-vs-verified-event/",
    "ownerType": "comparison",
    "proposition": "Source-derived event and Independently verified event answer different evidentiary or operational questions and must remain separate.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Source-derived event and Independently verified event.",
    "slug": "clm-k07-cmp-018",
    "sourceIds": [
      "SRC-UNICODE-RUNIC-17",
      "SRC-UNICODE-UAX15-17",
      "SRC-RFC-3492",
      "SRC-RFC-5890",
      "SRC-RFC-5891"
    ],
    "sourceSections": [
      {
        "section": "Runic range and character names",
        "sourceId": "SRC-UNICODE-RUNIC-17",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.",
        "url": "https://www.unicode.org/charts/PDF/U16A0.pdf"
      },
      {
        "section": "Normalization forms and conformance",
        "sourceId": "SRC-UNICODE-UAX15-17",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.",
        "url": "https://www.unicode.org/reports/tr15/"
      },
      {
        "section": "Abstract and encoding algorithm",
        "sourceId": "SRC-RFC-3492",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Punycode reversibly encodes Unicode strings into a restricted ASCII form for IDNA use.",
        "url": "https://www.rfc-editor.org/rfc/rfc3492"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/trace-correction-vs-history-rewrite/#clm-k07-cmp-019",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-019",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-019.json",
    "name": "Trace correction versus History rewrite",
    "ownerAnchor": "clm-k07-cmp-019",
    "ownerId": "K07-CMP-019",
    "ownerRoute": "/comparisons/trace-correction-vs-history-rewrite/",
    "ownerType": "comparison",
    "proposition": "Trace correction and History rewrite answer different evidentiary or operational questions and must remain separate.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Trace correction and History rewrite.",
    "slug": "clm-k07-cmp-019",
    "sourceIds": [
      "SRC-W3C-PROV-O",
      "SRC-RFC-3161",
      "SRC-C2PA",
      "SRC-IN-TOTO"
    ],
    "sourceSections": [
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "RFC status and update chain",
        "sourceId": "SRC-RFC-3161",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.",
        "url": "https://www.rfc-editor.org/info/rfc3161/"
      },
      {
        "section": "Version history — 2.4",
        "sourceId": "SRC-C2PA",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.",
        "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/weighted-score-vs-decision-authority/#clm-k07-cmp-020",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-020",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-020.json",
    "name": "Weighted score versus Decision authority",
    "ownerAnchor": "clm-k07-cmp-020",
    "ownerId": "K07-CMP-020",
    "ownerRoute": "/comparisons/weighted-score-vs-decision-authority/",
    "ownerType": "comparison",
    "proposition": "Weighted score and Decision authority answer different evidentiary or operational questions and must remain separate.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Weighted score and Decision authority.",
    "slug": "clm-k07-cmp-020",
    "sourceIds": [
      "SRC-INL-CCE",
      "SRC-NIST-800-82R3",
      "SRC-NRC-10CFR-73-54"
    ],
    "sourceSections": [
      {
        "section": "CCE methodology",
        "sourceId": "SRC-INL-CCE",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.",
        "url": "https://inl.gov/national-security/cce/"
      },
      {
        "section": "Abstract",
        "sourceId": "SRC-NIST-800-82R3",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.",
        "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final"
      },
      {
        "section": "73.54(a)",
        "sourceId": "SRC-NRC-10CFR-73-54",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.",
        "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/scheduler-definition-vs-observation/#clm-k07-cmp-021",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-021",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-021.json",
    "name": "Scheduler definition versus Observation evidence",
    "ownerAnchor": "clm-k07-cmp-021",
    "ownerId": "K07-CMP-021",
    "ownerRoute": "/comparisons/scheduler-definition-vs-observation/",
    "ownerType": "comparison",
    "proposition": "Scheduler definition and Observation evidence answer different evidentiary or operational questions and must remain separate.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Scheduler definition and Observation evidence.",
    "slug": "clm-k07-cmp-021",
    "sourceIds": [
      "SRC-W3C-PROV-O",
      "SRC-RFC-3161",
      "SRC-C2PA",
      "SRC-IN-TOTO"
    ],
    "sourceSections": [
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "RFC status and update chain",
        "sourceId": "SRC-RFC-3161",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.",
        "url": "https://www.rfc-editor.org/info/rfc3161/"
      },
      {
        "section": "Version history — 2.4",
        "sourceId": "SRC-C2PA",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.",
        "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/version-negotiation-vs-authorization/#clm-k07-cmp-022",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-022",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-022.json",
    "name": "Version negotiation versus Authorization",
    "ownerAnchor": "clm-k07-cmp-022",
    "ownerId": "K07-CMP-022",
    "ownerRoute": "/comparisons/version-negotiation-vs-authorization/",
    "ownerType": "comparison",
    "proposition": "Version negotiation and Authorization answer different evidentiary or operational questions and must remain separate.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Version negotiation and Authorization.",
    "slug": "clm-k07-cmp-022",
    "sourceIds": [
      "SRC-UNICODE-RUNIC-17",
      "SRC-UNICODE-UAX15-17",
      "SRC-RFC-5646",
      "SRC-W3C-PROV-O"
    ],
    "sourceSections": [
      {
        "section": "Runic range and character names",
        "sourceId": "SRC-UNICODE-RUNIC-17",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.",
        "url": "https://www.unicode.org/charts/PDF/U16A0.pdf"
      },
      {
        "section": "Normalization forms and conformance",
        "sourceId": "SRC-UNICODE-UAX15-17",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.",
        "url": "https://www.unicode.org/reports/tr15/"
      },
      {
        "section": "Language-tag structure and semantics",
        "sourceId": "SRC-RFC-5646",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Language tags identify the language and optional script or region of an information object.",
        "url": "https://www.rfc-editor.org/rfc/rfc5646"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/canonicalization-vs-authentication/#clm-k07-cmp-023",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-023",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-023.json",
    "name": "Canonicalization versus Authentication",
    "ownerAnchor": "clm-k07-cmp-023",
    "ownerId": "K07-CMP-023",
    "ownerRoute": "/comparisons/canonicalization-vs-authentication/",
    "ownerType": "comparison",
    "proposition": "Canonicalization and Authentication answer different evidentiary or operational questions and must remain separate.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Canonicalization and Authentication.",
    "slug": "clm-k07-cmp-023",
    "sourceIds": [
      "SRC-UNICODE-RUNIC-17",
      "SRC-UNICODE-UAX15-17",
      "SRC-RFC-5646",
      "SRC-W3C-PROV-O"
    ],
    "sourceSections": [
      {
        "section": "Runic range and character names",
        "sourceId": "SRC-UNICODE-RUNIC-17",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.",
        "url": "https://www.unicode.org/charts/PDF/U16A0.pdf"
      },
      {
        "section": "Normalization forms and conformance",
        "sourceId": "SRC-UNICODE-UAX15-17",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.",
        "url": "https://www.unicode.org/reports/tr15/"
      },
      {
        "section": "Language-tag structure and semantics",
        "sourceId": "SRC-RFC-5646",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Language tags identify the language and optional script or region of an information object.",
        "url": "https://www.rfc-editor.org/rfc/rfc5646"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/replay-detection-vs-freshness-truth/#clm-k07-cmp-024",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-024",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-024.json",
    "name": "Replay detection versus Freshness and truth",
    "ownerAnchor": "clm-k07-cmp-024",
    "ownerId": "K07-CMP-024",
    "ownerRoute": "/comparisons/replay-detection-vs-freshness-truth/",
    "ownerType": "comparison",
    "proposition": "Replay detection and Freshness and truth answer different evidentiary or operational questions and must remain separate.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Replay detection and Freshness and truth.",
    "slug": "clm-k07-cmp-024",
    "sourceIds": [
      "SRC-UNICODE-RUNIC-17",
      "SRC-UNICODE-UAX15-17",
      "SRC-RFC-5646",
      "SRC-W3C-PROV-O"
    ],
    "sourceSections": [
      {
        "section": "Runic range and character names",
        "sourceId": "SRC-UNICODE-RUNIC-17",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.",
        "url": "https://www.unicode.org/charts/PDF/U16A0.pdf"
      },
      {
        "section": "Normalization forms and conformance",
        "sourceId": "SRC-UNICODE-UAX15-17",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.",
        "url": "https://www.unicode.org/reports/tr15/"
      },
      {
        "section": "Language-tag structure and semantics",
        "sourceId": "SRC-RFC-5646",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Language tags identify the language and optional script or region of an information object.",
        "url": "https://www.rfc-editor.org/rfc/rfc5646"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/review-queue-vs-verified-history/#clm-k07-cmp-025",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-025",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-025.json",
    "name": "Primary-source review queue versus Verified history record",
    "ownerAnchor": "clm-k07-cmp-025",
    "ownerId": "K07-CMP-025",
    "ownerRoute": "/comparisons/review-queue-vs-verified-history/",
    "ownerType": "comparison",
    "proposition": "Primary-source review queue and Verified history record answer different evidentiary or operational questions and must remain separate.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Primary-source review queue and Verified history record.",
    "slug": "clm-k07-cmp-025",
    "sourceIds": [
      "SRC-UNICODE-RUNIC-17",
      "SRC-UNICODE-UAX15-17",
      "SRC-RFC-3492",
      "SRC-RFC-5890",
      "SRC-RFC-5891"
    ],
    "sourceSections": [
      {
        "section": "Runic range and character names",
        "sourceId": "SRC-UNICODE-RUNIC-17",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.",
        "url": "https://www.unicode.org/charts/PDF/U16A0.pdf"
      },
      {
        "section": "Normalization forms and conformance",
        "sourceId": "SRC-UNICODE-UAX15-17",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.",
        "url": "https://www.unicode.org/reports/tr15/"
      },
      {
        "section": "Abstract and encoding algorithm",
        "sourceId": "SRC-RFC-3492",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Punycode reversibly encodes Unicode strings into a restricted ASCII form for IDNA use.",
        "url": "https://www.rfc-editor.org/rfc/rfc3492"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/idn-snapshot-vs-live-service/#clm-k07-cmp-026",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-026",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-026.json",
    "name": "Offline IDN snapshot versus Live service",
    "ownerAnchor": "clm-k07-cmp-026",
    "ownerId": "K07-CMP-026",
    "ownerRoute": "/comparisons/idn-snapshot-vs-live-service/",
    "ownerType": "comparison",
    "proposition": "Offline IDN snapshot and Live service answer different evidentiary or operational questions and must remain separate.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Offline IDN snapshot and Live service.",
    "slug": "clm-k07-cmp-026",
    "sourceIds": [
      "SRC-UNICODE-RUNIC-17",
      "SRC-UNICODE-UAX15-17",
      "SRC-RFC-3492",
      "SRC-RFC-5890",
      "SRC-RFC-5891"
    ],
    "sourceSections": [
      {
        "section": "Runic range and character names",
        "sourceId": "SRC-UNICODE-RUNIC-17",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.",
        "url": "https://www.unicode.org/charts/PDF/U16A0.pdf"
      },
      {
        "section": "Normalization forms and conformance",
        "sourceId": "SRC-UNICODE-UAX15-17",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.",
        "url": "https://www.unicode.org/reports/tr15/"
      },
      {
        "section": "Abstract and encoding algorithm",
        "sourceId": "SRC-RFC-3492",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Punycode reversibly encodes Unicode strings into a restricted ASCII form for IDNA use.",
        "url": "https://www.rfc-editor.org/rfc/rfc3492"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/three-way-merge-vs-owner-decision/#clm-k07-cmp-027",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-027",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-027.json",
    "name": "Three-way merge versus Owner decision",
    "ownerAnchor": "clm-k07-cmp-027",
    "ownerId": "K07-CMP-027",
    "ownerRoute": "/comparisons/three-way-merge-vs-owner-decision/",
    "ownerType": "comparison",
    "proposition": "Three-way merge and Owner decision answer different evidentiary or operational questions and must remain separate.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Three-way merge and Owner decision.",
    "slug": "clm-k07-cmp-027",
    "sourceIds": [
      "SRC-INL-CCE",
      "SRC-NIST-800-82R3",
      "SRC-NRC-10CFR-73-54"
    ],
    "sourceSections": [
      {
        "section": "CCE methodology",
        "sourceId": "SRC-INL-CCE",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.",
        "url": "https://inl.gov/national-security/cce/"
      },
      {
        "section": "Abstract",
        "sourceId": "SRC-NIST-800-82R3",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.",
        "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final"
      },
      {
        "section": "73.54(a)",
        "sourceId": "SRC-NRC-10CFR-73-54",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.",
        "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/cut-set-vs-attack-path/#clm-k07-cmp-028",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-028",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-028.json",
    "name": "Abstract cut set versus Protected attack path",
    "ownerAnchor": "clm-k07-cmp-028",
    "ownerId": "K07-CMP-028",
    "ownerRoute": "/comparisons/cut-set-vs-attack-path/",
    "ownerType": "comparison",
    "proposition": "Abstract cut set and Protected attack path answer different evidentiary or operational questions and must remain separate.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Abstract cut set and Protected attack path.",
    "slug": "clm-k07-cmp-028",
    "sourceIds": [
      "SRC-INL-CCE",
      "SRC-NIST-800-82R3",
      "SRC-NRC-10CFR-73-54"
    ],
    "sourceSections": [
      {
        "section": "CCE methodology",
        "sourceId": "SRC-INL-CCE",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.",
        "url": "https://inl.gov/national-security/cce/"
      },
      {
        "section": "Abstract",
        "sourceId": "SRC-NIST-800-82R3",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.",
        "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final"
      },
      {
        "section": "73.54(a)",
        "sourceId": "SRC-NRC-10CFR-73-54",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.",
        "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/transition-plan-vs-deployment/#clm-k07-cmp-029",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-029",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-029.json",
    "name": "Cryptographic transition plan versus Deployed cryptographic state",
    "ownerAnchor": "clm-k07-cmp-029",
    "ownerId": "K07-CMP-029",
    "ownerRoute": "/comparisons/transition-plan-vs-deployment/",
    "ownerType": "comparison",
    "proposition": "Cryptographic transition plan and Deployed cryptographic state answer different evidentiary or operational questions and must remain separate.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Cryptographic transition plan and Deployed cryptographic state.",
    "slug": "clm-k07-cmp-029",
    "sourceIds": [
      "SRC-W3C-PROV-O",
      "SRC-RFC-3161",
      "SRC-C2PA",
      "SRC-IN-TOTO"
    ],
    "sourceSections": [
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "RFC status and update chain",
        "sourceId": "SRC-RFC-3161",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.",
        "url": "https://www.rfc-editor.org/info/rfc3161/"
      },
      {
        "section": "Version history — 2.4",
        "sourceId": "SRC-C2PA",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.",
        "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/evaluation-audit-vs-award/#clm-k07-cmp-030",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-030",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-030.json",
    "name": "Evaluation audit trail versus Procurement award",
    "ownerAnchor": "clm-k07-cmp-030",
    "ownerId": "K07-CMP-030",
    "ownerRoute": "/comparisons/evaluation-audit-vs-award/",
    "ownerType": "comparison",
    "proposition": "Evaluation audit trail and Procurement award answer different evidentiary or operational questions and must remain separate.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Evaluation audit trail and Procurement award.",
    "slug": "clm-k07-cmp-030",
    "sourceIds": [
      "SRC-INL-CCE",
      "SRC-NIST-800-82R3",
      "SRC-NRC-10CFR-73-54"
    ],
    "sourceSections": [
      {
        "section": "CCE methodology",
        "sourceId": "SRC-INL-CCE",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.",
        "url": "https://inl.gov/national-security/cce/"
      },
      {
        "section": "Abstract",
        "sourceId": "SRC-NIST-800-82R3",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.",
        "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final"
      },
      {
        "section": "73.54(a)",
        "sourceId": "SRC-NRC-10CFR-73-54",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.",
        "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/redaction-schema-vs-access-control/#clm-k07-cmp-031",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-031",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-031.json",
    "name": "Redaction and release schema versus Production access control",
    "ownerAnchor": "clm-k07-cmp-031",
    "ownerId": "K07-CMP-031",
    "ownerRoute": "/comparisons/redaction-schema-vs-access-control/",
    "ownerType": "comparison",
    "proposition": "Redaction and release schema and Production access control answer different evidentiary or operational questions and must remain separate.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Redaction and release schema and Production access control.",
    "slug": "clm-k07-cmp-031",
    "sourceIds": [
      "SRC-W3C-PROV-O",
      "SRC-RFC-3161",
      "SRC-C2PA",
      "SRC-IN-TOTO"
    ],
    "sourceSections": [
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "RFC status and update chain",
        "sourceId": "SRC-RFC-3161",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.",
        "url": "https://www.rfc-editor.org/info/rfc3161/"
      },
      {
        "section": "Version history — 2.4",
        "sourceId": "SRC-C2PA",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.",
        "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/state-machine-vs-runtime/#clm-k07-cmp-032",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-032",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-032.json",
    "name": "Protocol state machine versus Production runtime",
    "ownerAnchor": "clm-k07-cmp-032",
    "ownerId": "K07-CMP-032",
    "ownerRoute": "/comparisons/state-machine-vs-runtime/",
    "ownerType": "comparison",
    "proposition": "Protocol state machine and Production runtime answer different evidentiary, governance, or operational questions and must remain separate.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Protocol state machine and Production runtime.",
    "slug": "clm-k07-cmp-032",
    "sourceIds": [
      "SRC-UNICODE-RUNIC-17",
      "SRC-UNICODE-UAX15-17",
      "SRC-RFC-5646",
      "SRC-W3C-PROV-O"
    ],
    "sourceSections": [
      {
        "section": "Runic range and character names",
        "sourceId": "SRC-UNICODE-RUNIC-17",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.",
        "url": "https://www.unicode.org/charts/PDF/U16A0.pdf"
      },
      {
        "section": "Normalization forms and conformance",
        "sourceId": "SRC-UNICODE-UAX15-17",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.",
        "url": "https://www.unicode.org/reports/tr15/"
      },
      {
        "section": "Language-tag structure and semantics",
        "sourceId": "SRC-RFC-5646",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Language tags identify the language and optional script or region of an information object.",
        "url": "https://www.rfc-editor.org/rfc/rfc5646"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/decoder-agreement-vs-authentication/#clm-k07-cmp-033",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-033",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-033.json",
    "name": "Independent decoder agreement versus Authentication",
    "ownerAnchor": "clm-k07-cmp-033",
    "ownerId": "K07-CMP-033",
    "ownerRoute": "/comparisons/decoder-agreement-vs-authentication/",
    "ownerType": "comparison",
    "proposition": "Independent decoder agreement and Authentication answer different evidentiary, governance, or operational questions and must remain separate.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Independent decoder agreement and Authentication.",
    "slug": "clm-k07-cmp-033",
    "sourceIds": [
      "SRC-UNICODE-RUNIC-17",
      "SRC-UNICODE-UAX15-17",
      "SRC-RFC-5646",
      "SRC-W3C-PROV-O"
    ],
    "sourceSections": [
      {
        "section": "Runic range and character names",
        "sourceId": "SRC-UNICODE-RUNIC-17",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.",
        "url": "https://www.unicode.org/charts/PDF/U16A0.pdf"
      },
      {
        "section": "Normalization forms and conformance",
        "sourceId": "SRC-UNICODE-UAX15-17",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.",
        "url": "https://www.unicode.org/reports/tr15/"
      },
      {
        "section": "Language-tag structure and semantics",
        "sourceId": "SRC-RFC-5646",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Language tags identify the language and optional script or region of an information object.",
        "url": "https://www.rfc-editor.org/rfc/rfc5646"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/source-request-vs-accepted-evidence/#clm-k07-cmp-034",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-034",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-034.json",
    "name": "Source request versus Accepted evidence",
    "ownerAnchor": "clm-k07-cmp-034",
    "ownerId": "K07-CMP-034",
    "ownerRoute": "/comparisons/source-request-vs-accepted-evidence/",
    "ownerType": "comparison",
    "proposition": "Source request and Accepted evidence answer different evidentiary, governance, or operational questions and must remain separate.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Source request and Accepted evidence.",
    "slug": "clm-k07-cmp-034",
    "sourceIds": [
      "SRC-UNICODE-RUNIC-17",
      "SRC-UNICODE-UAX15-17",
      "SRC-RFC-3492",
      "SRC-RFC-5890",
      "SRC-RFC-5891"
    ],
    "sourceSections": [
      {
        "section": "Runic range and character names",
        "sourceId": "SRC-UNICODE-RUNIC-17",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.",
        "url": "https://www.unicode.org/charts/PDF/U16A0.pdf"
      },
      {
        "section": "Normalization forms and conformance",
        "sourceId": "SRC-UNICODE-UAX15-17",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.",
        "url": "https://www.unicode.org/reports/tr15/"
      },
      {
        "section": "Abstract and encoding algorithm",
        "sourceId": "SRC-RFC-3492",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Punycode reversibly encodes Unicode strings into a restricted ASCII form for IDNA use.",
        "url": "https://www.rfc-editor.org/rfc/rfc3492"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/signed-observation-vs-live-state/#clm-k07-cmp-035",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-035",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-035.json",
    "name": "Signed offline observation versus Live domain state",
    "ownerAnchor": "clm-k07-cmp-035",
    "ownerId": "K07-CMP-035",
    "ownerRoute": "/comparisons/signed-observation-vs-live-state/",
    "ownerType": "comparison",
    "proposition": "Signed offline observation and Live domain state answer different evidentiary, governance, or operational questions and must remain separate.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Signed offline observation and Live domain state.",
    "slug": "clm-k07-cmp-035",
    "sourceIds": [
      "SRC-UNICODE-RUNIC-17",
      "SRC-UNICODE-UAX15-17",
      "SRC-RFC-3492",
      "SRC-RFC-5890",
      "SRC-RFC-5891"
    ],
    "sourceSections": [
      {
        "section": "Runic range and character names",
        "sourceId": "SRC-UNICODE-RUNIC-17",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.",
        "url": "https://www.unicode.org/charts/PDF/U16A0.pdf"
      },
      {
        "section": "Normalization forms and conformance",
        "sourceId": "SRC-UNICODE-UAX15-17",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.",
        "url": "https://www.unicode.org/reports/tr15/"
      },
      {
        "section": "Abstract and encoding algorithm",
        "sourceId": "SRC-RFC-3492",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Punycode reversibly encodes Unicode strings into a restricted ASCII form for IDNA use.",
        "url": "https://www.rfc-editor.org/rfc/rfc3492"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/n-way-merge-vs-adjudication/#clm-k07-cmp-036",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-036",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-036.json",
    "name": "N-way merge versus Owner adjudication",
    "ownerAnchor": "clm-k07-cmp-036",
    "ownerId": "K07-CMP-036",
    "ownerRoute": "/comparisons/n-way-merge-vs-adjudication/",
    "ownerType": "comparison",
    "proposition": "N-way merge and Owner adjudication answer different evidentiary, governance, or operational questions and must remain separate.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between N-way merge and Owner adjudication.",
    "slug": "clm-k07-cmp-036",
    "sourceIds": [
      "SRC-INL-CCE",
      "SRC-NIST-800-82R3",
      "SRC-NRC-10CFR-73-54"
    ],
    "sourceSections": [
      {
        "section": "CCE methodology",
        "sourceId": "SRC-INL-CCE",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.",
        "url": "https://inl.gov/national-security/cce/"
      },
      {
        "section": "Abstract",
        "sourceId": "SRC-NIST-800-82R3",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.",
        "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final"
      },
      {
        "section": "73.54(a)",
        "sourceId": "SRC-NRC-10CFR-73-54",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.",
        "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/centrality-vs-vulnerability/#clm-k07-cmp-037",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-037",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-037.json",
    "name": "Dependency centrality versus Operational vulnerability",
    "ownerAnchor": "clm-k07-cmp-037",
    "ownerId": "K07-CMP-037",
    "ownerRoute": "/comparisons/centrality-vs-vulnerability/",
    "ownerType": "comparison",
    "proposition": "Dependency centrality and Operational vulnerability answer different evidentiary, governance, or operational questions and must remain separate.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Dependency centrality and Operational vulnerability.",
    "slug": "clm-k07-cmp-037",
    "sourceIds": [
      "SRC-INL-CCE",
      "SRC-NIST-800-82R3",
      "SRC-NRC-10CFR-73-54"
    ],
    "sourceSections": [
      {
        "section": "CCE methodology",
        "sourceId": "SRC-INL-CCE",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.",
        "url": "https://inl.gov/national-security/cce/"
      },
      {
        "section": "Abstract",
        "sourceId": "SRC-NIST-800-82R3",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.",
        "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final"
      },
      {
        "section": "73.54(a)",
        "sourceId": "SRC-NRC-10CFR-73-54",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.",
        "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/completeness-vs-deployment/#clm-k07-cmp-038",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-038",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-038.json",
    "name": "Evidence completeness versus Deployed cryptographic state",
    "ownerAnchor": "clm-k07-cmp-038",
    "ownerId": "K07-CMP-038",
    "ownerRoute": "/comparisons/completeness-vs-deployment/",
    "ownerType": "comparison",
    "proposition": "Evidence completeness and Deployed cryptographic state answer different evidentiary, governance, or operational questions and must remain separate.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Evidence completeness and Deployed cryptographic state.",
    "slug": "clm-k07-cmp-038",
    "sourceIds": [
      "SRC-W3C-PROV-O",
      "SRC-RFC-3161",
      "SRC-C2PA",
      "SRC-IN-TOTO"
    ],
    "sourceSections": [
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "RFC status and update chain",
        "sourceId": "SRC-RFC-3161",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.",
        "url": "https://www.rfc-editor.org/info/rfc3161/"
      },
      {
        "section": "Version history — 2.4",
        "sourceId": "SRC-C2PA",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.",
        "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/remand-vs-award/#clm-k07-cmp-039",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-039",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-039.json",
    "name": "Evaluation remand versus Procurement award",
    "ownerAnchor": "clm-k07-cmp-039",
    "ownerId": "K07-CMP-039",
    "ownerRoute": "/comparisons/remand-vs-award/",
    "ownerType": "comparison",
    "proposition": "Evaluation remand and Procurement award answer different evidentiary, governance, or operational questions and must remain separate.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Evaluation remand and Procurement award.",
    "slug": "clm-k07-cmp-039",
    "sourceIds": [
      "SRC-INL-CCE",
      "SRC-NIST-800-82R3",
      "SRC-NRC-10CFR-73-54"
    ],
    "sourceSections": [
      {
        "section": "CCE methodology",
        "sourceId": "SRC-INL-CCE",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.",
        "url": "https://inl.gov/national-security/cce/"
      },
      {
        "section": "Abstract",
        "sourceId": "SRC-NIST-800-82R3",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.",
        "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final"
      },
      {
        "section": "73.54(a)",
        "sourceId": "SRC-NRC-10CFR-73-54",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.",
        "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/result-chain-vs-running-scheduler/#clm-k07-cmp-040",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-040",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-040.json",
    "name": "Offline result chain versus Running scheduler",
    "ownerAnchor": "clm-k07-cmp-040",
    "ownerId": "K07-CMP-040",
    "ownerRoute": "/comparisons/result-chain-vs-running-scheduler/",
    "ownerType": "comparison",
    "proposition": "Offline result chain and Running scheduler answer different evidentiary, governance, or operational questions and must remain separate.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Offline result chain and Running scheduler.",
    "slug": "clm-k07-cmp-040",
    "sourceIds": [
      "SRC-W3C-PROV-O",
      "SRC-RFC-3161",
      "SRC-C2PA",
      "SRC-IN-TOTO"
    ],
    "sourceSections": [
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "RFC status and update chain",
        "sourceId": "SRC-RFC-3161",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.",
        "url": "https://www.rfc-editor.org/info/rfc3161/"
      },
      {
        "section": "Version history — 2.4",
        "sourceId": "SRC-C2PA",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.",
        "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/static-trend-vs-telemetry/#clm-k07-cmp-041",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-041",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-041.json",
    "name": "Static assurance trend versus Live telemetry",
    "ownerAnchor": "clm-k07-cmp-041",
    "ownerId": "K07-CMP-041",
    "ownerRoute": "/comparisons/static-trend-vs-telemetry/",
    "ownerType": "comparison",
    "proposition": "Static assurance trend and Live telemetry answer different evidentiary, governance, or operational questions and must remain separate.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Static assurance trend and Live telemetry.",
    "slug": "clm-k07-cmp-041",
    "sourceIds": [
      "SRC-INL-CCE",
      "SRC-NIST-800-82R3",
      "SRC-NRC-10CFR-73-54"
    ],
    "sourceSections": [
      {
        "section": "CCE methodology",
        "sourceId": "SRC-INL-CCE",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.",
        "url": "https://inl.gov/national-security/cce/"
      },
      {
        "section": "Abstract",
        "sourceId": "SRC-NIST-800-82R3",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.",
        "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final"
      },
      {
        "section": "73.54(a)",
        "sourceId": "SRC-NRC-10CFR-73-54",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.",
        "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/decoder-agreement-vs-security/#clm-k07-cmp-042",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-042",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-042.json",
    "name": "Decoder agreement versus Protocol security",
    "ownerAnchor": "clm-k07-cmp-042",
    "ownerId": "K07-CMP-042",
    "ownerRoute": "/comparisons/decoder-agreement-vs-security/",
    "ownerType": "comparison",
    "proposition": "Decoder agreement and Protocol security answer different evidentiary, governance, release, or operational questions and must remain separate.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Decoder agreement and Protocol security.",
    "slug": "clm-k07-cmp-042",
    "sourceIds": [
      "SRC-UNICODE-RUNIC-17",
      "SRC-UNICODE-UAX15-17",
      "SRC-RFC-5646",
      "SRC-W3C-PROV-O"
    ],
    "sourceSections": [
      {
        "section": "Runic range and character names",
        "sourceId": "SRC-UNICODE-RUNIC-17",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.",
        "url": "https://www.unicode.org/charts/PDF/U16A0.pdf"
      },
      {
        "section": "Normalization forms and conformance",
        "sourceId": "SRC-UNICODE-UAX15-17",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.",
        "url": "https://www.unicode.org/reports/tr15/"
      },
      {
        "section": "Language-tag structure and semantics",
        "sourceId": "SRC-RFC-5646",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Language tags identify the language and optional script or region of an information object.",
        "url": "https://www.rfc-editor.org/rfc/rfc5646"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/signature-validity-vs-historical-truth/#clm-k07-cmp-043",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-043",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-043.json",
    "name": "Signature validity versus Historical truth",
    "ownerAnchor": "clm-k07-cmp-043",
    "ownerId": "K07-CMP-043",
    "ownerRoute": "/comparisons/signature-validity-vs-historical-truth/",
    "ownerType": "comparison",
    "proposition": "Signature validity and Historical truth answer different evidentiary, governance, release, or operational questions and must remain separate.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Signature validity and Historical truth.",
    "slug": "clm-k07-cmp-043",
    "sourceIds": [
      "SRC-NIST-AI-RMF",
      "SRC-W3C-PROV-O",
      "SRC-EU-AI-ACT"
    ],
    "sourceSections": [
      {
        "section": "AI RMF 1.0 publication",
        "sourceId": "SRC-NIST-AI-RMF",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "NIST AI RMF 1.0 is a voluntary risk-management framework with Govern, Map, Measure, and Manage functions.",
        "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf"
      },
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "Application timeline",
        "sourceId": "SRC-EU-AI-ACT",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.",
        "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/encoding-consensus-vs-domain-operation/#clm-k07-cmp-044",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-044",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-044.json",
    "name": "Encoding consensus versus Domain operation",
    "ownerAnchor": "clm-k07-cmp-044",
    "ownerId": "K07-CMP-044",
    "ownerRoute": "/comparisons/encoding-consensus-vs-domain-operation/",
    "ownerType": "comparison",
    "proposition": "Encoding consensus and Domain operation answer different evidentiary, governance, release, or operational questions and must remain separate.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Encoding consensus and Domain operation.",
    "slug": "clm-k07-cmp-044",
    "sourceIds": [
      "SRC-UNICODE-RUNIC-17",
      "SRC-UNICODE-UAX15-17",
      "SRC-RFC-3492",
      "SRC-RFC-5890",
      "SRC-RFC-5891"
    ],
    "sourceSections": [
      {
        "section": "Runic range and character names",
        "sourceId": "SRC-UNICODE-RUNIC-17",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.",
        "url": "https://www.unicode.org/charts/PDF/U16A0.pdf"
      },
      {
        "section": "Normalization forms and conformance",
        "sourceId": "SRC-UNICODE-UAX15-17",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.",
        "url": "https://www.unicode.org/reports/tr15/"
      },
      {
        "section": "Abstract and encoding algorithm",
        "sourceId": "SRC-RFC-3492",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Punycode reversibly encodes Unicode strings into a restricted ASCII form for IDNA use.",
        "url": "https://www.rfc-editor.org/rfc/rfc3492"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/merge-result-vs-owner-decision/#clm-k07-cmp-045",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-045",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-045.json",
    "name": "Merge result versus Owner decision",
    "ownerAnchor": "clm-k07-cmp-045",
    "ownerId": "K07-CMP-045",
    "ownerRoute": "/comparisons/merge-result-vs-owner-decision/",
    "ownerType": "comparison",
    "proposition": "Merge result and Owner decision answer different evidentiary, governance, release, or operational questions and must remain separate.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Merge result and Owner decision.",
    "slug": "clm-k07-cmp-045",
    "sourceIds": [
      "SRC-INL-CCE",
      "SRC-NIST-800-82R3",
      "SRC-NRC-10CFR-73-54"
    ],
    "sourceSections": [
      {
        "section": "CCE methodology",
        "sourceId": "SRC-INL-CCE",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.",
        "url": "https://inl.gov/national-security/cce/"
      },
      {
        "section": "Abstract",
        "sourceId": "SRC-NIST-800-82R3",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.",
        "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final"
      },
      {
        "section": "73.54(a)",
        "sourceId": "SRC-NRC-10CFR-73-54",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.",
        "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/stress-fixture-vs-protected-architecture/#clm-k07-cmp-046",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-046",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-046.json",
    "name": "Stress fixture versus Protected architecture",
    "ownerAnchor": "clm-k07-cmp-046",
    "ownerId": "K07-CMP-046",
    "ownerRoute": "/comparisons/stress-fixture-vs-protected-architecture/",
    "ownerType": "comparison",
    "proposition": "Stress fixture and Protected architecture answer different evidentiary, governance, release, or operational questions and must remain separate.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Stress fixture and Protected architecture.",
    "slug": "clm-k07-cmp-046",
    "sourceIds": [
      "SRC-INL-CCE",
      "SRC-NIST-800-82R3",
      "SRC-NRC-10CFR-73-54"
    ],
    "sourceSections": [
      {
        "section": "CCE methodology",
        "sourceId": "SRC-INL-CCE",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.",
        "url": "https://inl.gov/national-security/cce/"
      },
      {
        "section": "Abstract",
        "sourceId": "SRC-NIST-800-82R3",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.",
        "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final"
      },
      {
        "section": "73.54(a)",
        "sourceId": "SRC-NRC-10CFR-73-54",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.",
        "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/crypto-gate-pass-vs-production-migration/#clm-k07-cmp-047",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-047",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-047.json",
    "name": "Crypto gate pass versus Production migration",
    "ownerAnchor": "clm-k07-cmp-047",
    "ownerId": "K07-CMP-047",
    "ownerRoute": "/comparisons/crypto-gate-pass-vs-production-migration/",
    "ownerType": "comparison",
    "proposition": "Crypto gate pass and Production migration answer different evidentiary, governance, release, or operational questions and must remain separate.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Crypto gate pass and Production migration.",
    "slug": "clm-k07-cmp-047",
    "sourceIds": [
      "SRC-W3C-PROV-O",
      "SRC-RFC-3161",
      "SRC-C2PA",
      "SRC-IN-TOTO"
    ],
    "sourceSections": [
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "RFC status and update chain",
        "sourceId": "SRC-RFC-3161",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.",
        "url": "https://www.rfc-editor.org/info/rfc3161/"
      },
      {
        "section": "Version history — 2.4",
        "sourceId": "SRC-C2PA",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.",
        "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/evaluation-replay-vs-award/#clm-k07-cmp-048",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-048",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-048.json",
    "name": "Evaluation replay versus Contract award",
    "ownerAnchor": "clm-k07-cmp-048",
    "ownerId": "K07-CMP-048",
    "ownerRoute": "/comparisons/evaluation-replay-vs-award/",
    "ownerType": "comparison",
    "proposition": "Evaluation replay and Contract award answer different evidentiary, governance, release, or operational questions and must remain separate.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Evaluation replay and Contract award.",
    "slug": "clm-k07-cmp-048",
    "sourceIds": [
      "SRC-INL-CCE",
      "SRC-NIST-800-82R3",
      "SRC-NRC-10CFR-73-54"
    ],
    "sourceSections": [
      {
        "section": "CCE methodology",
        "sourceId": "SRC-INL-CCE",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.",
        "url": "https://inl.gov/national-security/cce/"
      },
      {
        "section": "Abstract",
        "sourceId": "SRC-NIST-800-82R3",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.",
        "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final"
      },
      {
        "section": "73.54(a)",
        "sourceId": "SRC-NRC-10CFR-73-54",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.",
        "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/scheduler-simulation-vs-runtime/#clm-k07-cmp-049",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-049",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-049.json",
    "name": "Scheduler simulation versus Scheduler runtime",
    "ownerAnchor": "clm-k07-cmp-049",
    "ownerId": "K07-CMP-049",
    "ownerRoute": "/comparisons/scheduler-simulation-vs-runtime/",
    "ownerType": "comparison",
    "proposition": "Scheduler simulation and Scheduler runtime answer different evidentiary, governance, release, or operational questions and must remain separate.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Scheduler simulation and Scheduler runtime.",
    "slug": "clm-k07-cmp-049",
    "sourceIds": [
      "SRC-W3C-PROV-O",
      "SRC-RFC-3161",
      "SRC-C2PA",
      "SRC-IN-TOTO"
    ],
    "sourceSections": [
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "RFC status and update chain",
        "sourceId": "SRC-RFC-3161",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.",
        "url": "https://www.rfc-editor.org/info/rfc3161/"
      },
      {
        "section": "Version history — 2.4",
        "sourceId": "SRC-C2PA",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.",
        "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/taint-model-vs-enforcement/#clm-k07-cmp-050",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-050",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-050.json",
    "name": "Taint model versus Production enforcement",
    "ownerAnchor": "clm-k07-cmp-050",
    "ownerId": "K07-CMP-050",
    "ownerRoute": "/comparisons/taint-model-vs-enforcement/",
    "ownerType": "comparison",
    "proposition": "Taint model and Production enforcement answer different evidentiary, governance, release, or operational questions and must remain separate.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Taint model and Production enforcement.",
    "slug": "clm-k07-cmp-050",
    "sourceIds": [
      "SRC-W3C-PROV-O",
      "SRC-RFC-3161",
      "SRC-C2PA",
      "SRC-IN-TOTO"
    ],
    "sourceSections": [
      {
        "section": "Abstract and status",
        "sourceId": "SRC-W3C-PROV-O",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
        "url": "https://www.w3.org/TR/prov-o/#abstract"
      },
      {
        "section": "RFC status and update chain",
        "sourceId": "SRC-RFC-3161",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.",
        "url": "https://www.rfc-editor.org/info/rfc3161/"
      },
      {
        "section": "Version history — 2.4",
        "sourceId": "SRC-C2PA",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.",
        "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026"
      }
    ],
    "type": "ClaimRecord"
  },
  {
    "canonicalClaimUrl": "https://xn--mwe.com/comparisons/release-diff-vs-telemetry/#clm-k07-cmp-051",
    "claimStatus": "PROJECT DOCTRINE",
    "correctionStatus": "CURRENT K07 RECORD",
    "id": "CLM-K07-CMP-051",
    "lastReviewed": "2026-08-16",
    "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-051.json",
    "name": "Release diff versus Live telemetry",
    "ownerAnchor": "clm-k07-cmp-051",
    "ownerId": "K07-CMP-051",
    "ownerRoute": "/comparisons/release-diff-vs-telemetry/",
    "ownerType": "comparison",
    "proposition": "Release diff and Live telemetry answer different evidentiary, governance, release, or operational questions and must remain separate.",
    "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.",
    "releaseId": "K12-2026-08-16",
    "releaseVersion": "2.1.0",
    "researchCutoff": "2026-08-16",
    "scope": "K07 canonical distinction between Release diff and Live telemetry.",
    "slug": "clm-k07-cmp-051",
    "sourceIds": [
      "SRC-INL-CCE",
      "SRC-NIST-800-82R3",
      "SRC-NRC-10CFR-73-54"
    ],
    "sourceSections": [
      {
        "section": "CCE methodology",
        "sourceId": "SRC-INL-CCE",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.",
        "url": "https://inl.gov/national-security/cce/"
      },
      {
        "section": "Abstract",
        "sourceId": "SRC-NIST-800-82R3",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.",
        "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final"
      },
      {
        "section": "73.54(a)",
        "sourceId": "SRC-NRC-10CFR-73-54",
        "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT",
        "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.",
        "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54"
      }
    ],
    "type": "ClaimRecord"
  }
]