{
  "schema": "vedokrok.public-item.v1",
  "release_id": "MHC-RPUB-20260920-75ad787a",
  "url": "/knowledge/preserve-the-transformation-chain-with-the-artifact",
  "id": "MHC-D-RESEARCH-0421",
  "version": "0.1.0",
  "title": "Preserve the transformation chain with the artifact",
  "summary": "The final file is easier to trust when its journey did not disappear on the way.",
  "kind": "checklist",
  "body": "Keep a lineage record that links each material version to the prior version, the transformation performed, the actor or system, and the time or change identity. Prefer machine-bound hashes or immutable version IDs where the platform supports them. The chain should let a reviewer reconstruct how the final artifact came to exist.",
  "limits": [
    "Lineage metadata can expose sensitive information; store only what is required and protect the provenance record appropriately."
  ],
  "topics": [
    "union-provenance-verification"
  ],
  "intents": [],
  "source_ids": [
    "RS-B706646751C39412",
    "RS-FF258DEA21EDA7AB"
  ],
  "evidence": [
    {
      "claim": "C2PA 2.4 is designed to preserve provenance across a workflow by adding information about subsequent changes while retaining earlier provenance information.",
      "source_id": "RS-B706646751C39412",
      "role": "supports",
      "note": "Continuity depends on participating tools and workflows preserving or re-establishing the relevant credentials.",
      "locator": "Introduction and whole-workflow applicability"
    },
    {
      "claim": "The 2026 provenance-neglect paper defines provenance broadly as the recorded history of data origin, collection, transformation, processing and handling over time.",
      "source_id": "RS-FF258DEA21EDA7AB",
      "role": "supports",
      "note": "The paper adapts provenance concepts to news verification; other domains may require additional lineage fields.",
      "locator": "Definition of provenance neglect and data provenance"
    }
  ],
  "use_when": [
    "A document, dataset or media asset is repeatedly transformed before someone must audit the final result."
  ],
  "avoid_when": [
    "Lineage metadata can expose sensitive information; store only what is required and protect the provenance record appropriately."
  ],
  "example": "A data export records source snapshot, transformation script version, generated file hash and the import batch that consumed it.",
  "check": "A reviewer can trace the final artifact backward without relying on someone's memory of intermediate edits.",
  "checklist": [
    "Each material version has a stable identity.",
    "The predecessor or ingredient is named.",
    "The transformation is described at useful granularity.",
    "Actor/system and time or change identity are recorded.",
    "The final artifact can be connected back through the chain."
  ],
  "sources": [
    {
      "id": "RS-B706646751C39412",
      "title": "Content Credentials: C2PA Technical Specification 2.4",
      "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html"
    },
    {
      "id": "RS-FF258DEA21EDA7AB",
      "title": "The Original Sins of Algorithmic Authenticity Verification: Provenance Neglect and Model Collapse in AI-Mediated News and Information",
      "url": "https://www.tandfonline.com/doi/full/10.1080/08838151.2026.2691175"
    }
  ],
  "relations": [
    {
      "from": "MHC-D-RESEARCH-0421",
      "to": "MHC-D-RESEARCH-0422",
      "type": "useful_with",
      "url": "/knowledge/bind-the-verification-to-the-exact-artifact-reviewed"
    }
  ],
  "collections": [
    {
      "id": "RC-3F875FF96207B5CE",
      "title": "Trace where information came from before deciding whether to trust it",
      "url": "/collections/trace-where-information-came-from-before-deciding-whether-to-trust-it"
    }
  ]
}