# Do not confuse authentic provenance with factual truth

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Do not confuse authentic provenance with factual truth

ID: MHC-D-RESEARCH-0419 · Version: 0.1.0 · Kind: principle
Source: https://vedokrok.com/knowledge/do-not-confuse-authentic-provenance-with-factual-truth

Knowing exactly who made a statement does not make the statement correct.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### 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.

### Explanation

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.

### 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.

### 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.

### Evidence and sources

- supports: 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. — RS-36D653DA482EBF19. Factual verification still requires evidence about the claim itself. (Can provenance information determine whether an asset depicts the truth?)
- RS-36D653DA482EBF19: C2PA and Content Credentials Explainer — https://spec.c2pa.org/specifications/specifications/2.2/explainer/Explainer.html

No review details supplied.
Related (use_before): https://vedokrok.com/knowledge/separate-creator-identity-from-claim-support
