Reading an ingredient chain in a mixed-media project
A practical method for reviewing sources, edits and missing context in composite media.
The short answer
C2PA ingredients describe declared relationships between an asset and sources used in its creation or editing. They are not a guarantee that every contributing source or earlier step is present. Review the relationship type, available validation information and missing references when documenting a composite's provenance.
Source context: SDK: building manifests with ingredients. The workflow recommendations below are editorial analysis.
A project is rarely a single origin story
An advertisement might combine camera footage, a generated sky, licensed music and a title animation. Asking whether the whole project is “AI” hides the decisions a reviewer actually needs to make. Begin with a component inventory in plain language, then compare it with any ingredient information the final asset supplies.
Ingredient records can help describe provenance relationships, but they are not a complete editing project by default. A summary listing two ingredients does not tell you that exactly two sources were ever used. Read the available declaration, note omissions and ask the editor for context where the record cannot answer the question.
Trace a source relationship carefully
Pick one source you know belongs in the composition. Inspect its original, then inspect the final asset. Record the source title and relationship fields where available, and distinguish the active declaration from references to earlier ones. If an ingredient’s history reports a problem, keep that issue visible rather than letting a clean headline for the final asset conceal it.
Titles are useful for a human discussion but can be ambiguous. Two sources can share a filename, and a renamed export can carry the same pixels. Preserve the exact inspection records and acquisition context so reviewers can understand the relationship without relying solely on a friendly label.
Handoff the gaps as well as the links
Write an accompanying note identifying the generated, captured and licensed components. Keep permissions and usage rights in a separate production record: a provenance chain is not a substitute for a license agreement. The client needs both a technical account of the file and the authorization to use its content.
If the final record does not preserve a source you expected, test the import and export path with a simple project. Add one ingredient at a time to isolate behavior. That experiment is more useful than manually adding a source name to JSON and calling the history repaired. A later declaration cannot retroactively prove what happened in an undocumented earlier step.
A comparison for your review
| Production record | Purpose | Do not confuse with |
|---|---|---|
| Component inventory | Explain what was used | Complete machine-verified history |
| Ingredient relationship | Describe a recorded source link | Copyright permission |
| Rights documentation | Authorize intended use | Cryptographic validation |
Put it into practice
- Create a human-readable component inventory.
- Inspect known source files separately.
- Review ingredient validation issues.
- Preserve rights documentation independently.
- Reproduce unexpected gaps with a small project.
Bring your own evidence.
Inspect a local file and see what it actually declares.