# Treat a provenance gap as an unknown, not a verdict

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
Editorial overlay: MHC-EO-20261021-481e1ce95099
Editorial projection SHA-256: 6b41bfd164b85b2522e2378c425929aa041d9e093e81428ade9a7b7b9f78e8fe

---

## Treat a provenance gap as an unknown, not a verdict

ID: MHC-D-RESEARCH-0420 · Version: 0.1.0 · Kind: heuristic
Source: https://vedokrok.com/knowledge/treat-a-provenance-gap-as-an-unknown-not-a-verdict

A missing receipt is not automatically evidence of theft.

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

### Use when

- A content history has a missing transformation or loses credentials at some point in the chain.

### Avoid when

- Some provenance loss may itself violate a required control or policy even when it does not prove the content is false.

### Explanation

Mark the missing interval explicitly and ask what explanations fit it: unsupported editing software, export/re-encoding, deliberate removal or another workflow break. Increase verification effort around the gap, but do not label the asset false or malicious from absence alone. The useful state is 'provenance incomplete here.'

### Example

An image retains a publisher credential but lacks metadata for one crop step performed in a non-aware editor; record the gap rather than inventing the edit history.

### Check

The review distinguishes missing provenance from verified manipulation and names the next evidence needed.

### Limits

- Some provenance loss may itself violate a required control or policy even when it does not prove the content is false.

### Evidence and sources

- supports: C2PA guidance states that provenance can be incomplete when modifications occur in tools or workflows that do not update Content Credentials. — RS-36D653DA482EBF19. Missing provenance is not automatically evidence of malicious tampering; the gap must be interpreted in context. (Is provenance always complete?)
- RS-36D653DA482EBF19: C2PA and Content Credentials Explainer — https://spec.c2pa.org/specifications/specifications/2.2/explainer/Explainer.html

### Vedokrok editorial review

Distinguish missing history from a failed file binding

A missing edit record and a credential that does not match this file are different findings. Neither, by itself, tells you whether the content’s claims are true.

#### Record the actual validation result

Check whether credentials are absent, whether the recorded history has a gap, or whether validation of the current file failed. Do not label a failed binding merely as an undocumented edit. Keep the validator’s result and the exact file you checked, then request the relevant original or export history if needed.

#### Do not invent the missing link

An edit outside a credential-aware workflow may leave a gap. A later, valid credential can cover the current asset without documenting every earlier step. For example, a resized diagram may receive new credentials at publication; that does not reconstruct the missing editing history. Credentials left over from an earlier file do not automatically validate the changed file.

**Editorial takeaway:** Report the gap or validation failure, what remains trustworthy, and the next evidence needed. Content accuracy and any required provenance policy still need separate checks.

#### Editorial evidence

- supports: Incomplete provenance can coexist with a later active credential. — RS-36D653DA482EBF19. Selected official passage inspected on 2026-10-04. The original example omitted the later active-credential condition. (Version 2.2 explainer, section 7.2.1)
- supports: A nonmatching content hash can require rejection of the manifest. — SRC-C2PA-2-4. Selected normative passage inspected. This is a conceptual distinction, not a complete validator implementation recipe. (Version 2.4, section 15.12.1.1; assertion.dataHash.mismatch)
- limits: Provenance alone does not establish factual truth. — RS-36D653DA482EBF19. Missing history, validation failure and factual falsity must not be collapsed into one conclusion. (Version 2.2 explainer, section 7.2.2)
- RS-36D653DA482EBF19: C2PA and Content Credentials Explainer — https://spec.c2pa.org/specifications/specifications/2.2/explainer/Explainer.html
- SRC-C2PA-2-4: Content Credentials: C2PA Technical Specification 2.4 — https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html

Editorial version: 1.0.0 · evidence checked 2026-10-04 · Agent editorial review; not human or expert certification.

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/verify-each-ingredient-at-the-level-the-evidence-allows
