{
  "schema": "vedokrok.public-item.v1",
  "release_id": "MHC-RPUB-20260920-75ad787a",
  "url": "/knowledge/do-not-confuse-authentic-provenance-with-factual-truth",
  "id": "MHC-D-RESEARCH-0419",
  "version": "0.1.0",
  "title": "Do not confuse authentic provenance with factual truth",
  "summary": "Knowing exactly who made a statement does not make the statement correct.",
  "kind": "principle",
  "body": "Use provenance to answer origin and history questions: who or what created the asset, how it changed, and whether the recorded chain is intact. Verify factual claims separately against appropriate evidence. A well-authenticated mistake is still a mistake; an unsigned claim can still be true but harder to authenticate.",
  "limits": [
    "Provenance can materially increase trust in origin and integrity; the rule is not to ignore it, but to avoid promoting it into semantic truth."
  ],
  "topics": [
    "union-provenance-verification"
  ],
  "intents": [],
  "source_ids": [
    "RS-36D653DA482EBF19"
  ],
  "evidence": [
    {
      "claim": "C2PA explicitly states that provenance can provide evidence about origin, history and authenticity but cannot by itself determine whether content is true, accurate or factual.",
      "source_id": "RS-36D653DA482EBF19",
      "role": "supports",
      "note": "Factual verification still requires evidence about the claim itself.",
      "locator": "Can provenance information determine whether an asset depicts the truth?"
    }
  ],
  "use_when": [
    "A file, image, document or AI output has strong provenance metadata and the team is tempted to treat that as proof of the claim inside it."
  ],
  "avoid_when": [
    "Provenance can materially increase trust in origin and integrity; the rule is not to ignore it, but to avoid promoting it into semantic truth."
  ],
  "example": "A signed company screenshot proves the image came through that workflow; it does not prove the chart's underlying numbers are correct.",
  "check": "The verification record contains separate conclusions for provenance/authenticity and factual support.",
  "sources": [
    {
      "id": "RS-36D653DA482EBF19",
      "title": "C2PA and Content Credentials Explainer",
      "url": "https://spec.c2pa.org/specifications/specifications/2.2/explainer/Explainer.html"
    }
  ],
  "relations": [
    {
      "from": "MHC-D-RESEARCH-0419",
      "to": "MHC-D-RESEARCH-0426",
      "type": "use_before",
      "url": "/knowledge/separate-creator-identity-from-claim-support"
    }
  ],
  "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"
    }
  ]
}