{
  "canonicalClaimUrl": "https://xn--mwe.com/questions/what-is-supersession-chain/#clm-k03-q-063",
  "claimStatus": "VERIFIED PROJECT IMPLEMENTATION",
  "correctionStatus": "CURRENT K03 RECORD",
  "id": "CLM-K03-Q-063",
  "lastReviewed": "2026-08-14",
  "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-063.json",
  "name": "What is a supersession chain?",
  "ownerAnchor": "clm-k03-q-063",
  "ownerId": "K01-Q-063",
  "ownerRoute": "/questions/what-is-supersession-chain/",
  "ownerType": "question",
  "proposition": "A supersession chain links each replaced source, decision, release, or record model to its active successor for a defined scope while preserving historical availability and effective dates. It prevents an obsolete record from remaining silently active and avoids deleting the evidence of prior reliance.",
  "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.",
  "releaseId": "K12-2026-08-16",
  "releaseVersion": "2.1.0",
  "researchCutoff": "2026-08-14",
  "scope": "Direct answer for What is a supersession chain?",
  "slug": "clm-k03-q-063",
  "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"
}