Concept
Keep creation, transformation and claim layers separate
One green badge can hide three different questions.
When it fits
- A verification note compresses asset origin, editing history and factual assessment into one label such as 'trusted.'
When to avoid it
- Consumer interfaces may summarize these layers, but the underlying review should not collapse them if the distinction affects decisions.
The idea
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.
An 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 your result
Changing one layer—such as discovering an edit—does not automatically overwrite conclusions about the other layers.
Keep this limit in mind
- Consumer interfaces may summarize these layers, but the underlying review should not collapse them if the distinction affects decisions.
Connected ideas
Useful withDo not confuse authentic provenance with factual truth
Evidence and sources
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.
The practical separation is an editorial inference from the standard's explicit boundary and should be adapted to the domain.
C2PA and Content Credentials Explainer · Provenance versus truth
Current C2PA specifications use ingredients and actions to represent how prior assets contribute to a new asset and how it was transformed over time.
A complete semantic data-lineage system may need domain-specific transformations beyond media-oriented C2PA assertions.
Content Credentials Specification 2.4 · Assertions, actions and ingredients