Asset provenance handoff: make a receipt, not a mythology

Give every deliverable a human-readable receipt

The receipt travels with one final asset, not with an entire campaign folder. Start with asset ID, filename, file hash, export date, owner, approved channels, territories, expiration if any, and the exact final version. Then name the source assets, contributors, tool or model steps when known, and the approvals performed. Use links or IDs rather than embedding confidential inputs in a file that will travel to a media partner.

A receipt should answer practical questions quickly: what is this? where did it come from? who may use it? what needs checking before reuse? who can withdraw it? If it cannot answer those, it is a retrospective scrapbook rather than a production handoff.

Separate declared history from verified checks

Use two columns. Declared history is what the operator, vendor or contributor recorded: prompt ID, source image ID, model, edit steps and contributor. Verified checks are what a named reviewer actually assessed: product fidelity, copy, talent release existence, music cue sheet existence, accessibility, brand approval and export match. Do not upgrade a declaration into a verified fact simply because it appears in metadata.

The C2PA specification defines signed claims, assertions, ingredients and validation states for content provenance. Its validation codes include missing, unknown and mismatched conditions. That technical record can help a team detect whether a declared chain validates; it does not answer whether a source image was licensed, a product claim is true, or an audience has been told enough.

Source context: Content Credentials: C2PA Technical Specification

Use the minimum receipt fields

Our recommended receipt has eight blocks: identity; final-file integrity; approved use; source inputs; production declaration; people and rights records; review evidence; and aftercare. Under aftercare, include the correction or takedown owner, the date to recheck a time-sensitive offer, and the replacement asset ID if one exists. Keep legal releases and sensitive contracts in their controlled repository; the receipt only points to the record and its scope.

If C2PA Content Credentials are available, attach or link the validated result and record the validator and time checked. If they are absent, say absent. A blank field is better than an invented origin story. The same is true of model detail: record ‘vendor did not provide’ rather than guessing from a visual style.

• Asset identity: ID, hash, final file and exact export.
• Use scope: channel, territory, term, audience or placement limits.
• Review: named check, reviewer, date, version and result.
• Aftercare: correction, withdrawal and replacement owner.

Handoff is complete only when reuse is bounded

Before sending a package, ask the recipient to answer three questions from the receipt: may we run this in this channel? can we resize or localize it? who do we call if it must come down? If those cannot be answered, the package is incomplete even if it contains immaculate source metadata.

Preserve the receipt with the final asset and with the campaign register. Re-exporting, cropping or combining a file creates a new deliverable and should create a new receipt that points back to its ingredients. That extra step is not bureaucracy for its own sake; it prevents a valid approval for one placement becoming a vague permission for every future use.