# Keep creation, transformation and claim layers separate

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

---

## Keep creation, transformation and claim layers separate

ID: MHC-D-RESEARCH-0427 · Version: 0.1.0 · Kind: concept
Source: https://vedokrok.com/knowledge/keep-creation-transformation-and-claim-layers-separate

One green badge can hide three different questions.

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

### Use when

- A verification note compresses asset origin, editing history and factual assessment into one label such as 'trusted.'

### Avoid when

- Consumer interfaces may summarize these layers, but the underlying review should not collapse them if the distinction affects decisions.

### Explanation

Maintain separate fields or judgments for creation provenance, transformation history and semantic claim support. A clean creation chain can coexist with heavy editing; heavy editing can be legitimate; either asset can contain true or false claims. The separation makes later corrections and risk decisions more precise.

### Example

An AI-edited product image may have clear provenance and disclosed edits while a marketing claim printed on it still needs separate evidence.

### Check

Changing one layer—such as discovering an edit—does not automatically overwrite conclusions about the other layers.

### Limits

- Consumer interfaces may summarize these layers, but the underlying review should not collapse them if the distinction affects decisions.

### Evidence and sources

- supports: C2PA separates provenance declarations about creation and transformation from the content's semantic truth, implying that who made an asset, how it changed and whether its claims are supported are different questions. — RS-36D653DA482EBF19. The practical separation is an editorial inference from the standard's explicit boundary and should be adapted to the domain. (Provenance versus truth)
- supports: Current C2PA specifications use ingredients and actions to represent how prior assets contribute to a new asset and how it was transformed over time. — RS-3271B136C6377DC1. A complete semantic data-lineage system may need domain-specific transformations beyond media-oriented C2PA assertions. (Assertions, actions and ingredients)
- RS-36D653DA482EBF19: C2PA and Content Credentials Explainer — https://spec.c2pa.org/specifications/specifications/2.2/explainer/Explainer.html
- RS-3271B136C6377DC1: Content Credentials Specification 2.4 — https://spec.c2pa.org/specifications/specifications/2.4/specs/ContentCredentials.html

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/do-not-confuse-authentic-provenance-with-factual-truth
