Which model generated it?
Was this Runway? Kling? A self-hosted model? Without a signed record, you're trusting a verbal claim.
AI-generated video is entering publishing, advertising, education, and regulated content. The question is no longer "can AI make video?" but "can you prove where it came from?" C2PA provenance is the answer the industry is converging on. This guide explains what it is, how it works at the per-shot level, and why it matters before you distribute.
The Coalition for Content Provenance and Authenticity (C2PA) is a technical standard — not a product, not a brand. It defines how digital content can carry a signed, tamper-evident manifest that records its origin, creation method, and chain of custody.
Think of it as a notarized chain of custody for digital files. The manifest travels with the content. Anyone downstream — a publisher, a platform, a legal reviewer — can verify the chain without trusting the person who sent it.
C2PA was developed by Adobe, Microsoft, Intel, the BBC, and others. It is an open standard (ISO under development). It is not proprietary to any single vendor.
When a human shoots footage with a camera, provenance is implicit — someone was there, the camera recorded it. When AI generates video, that implicit trust disappears. The content exists because software produced it. Without provenance, there is no verifiable answer to basic questions:
Was this Runway? Kling? A self-hosted model? Without a signed record, you're trusting a verbal claim.
Which operator reviewed and approved each shot? In a team production, this matters for accountability.
Regulators and legal teams increasingly want to know the input, not just the output. A manifest can record the prompt hash.
If an AI likeness appears in a shot, is there a license attestation attached to that specific shot? Or just a verbal "we had permission"?
Without provenance, every AI video is a black box. With C2PA, each piece of content carries its own verifiable answer.
Most C2PA implementations sign the final exported file. That tells you "this MP4 was created by software X." It does not tell you what happened inside the production.
A production is not one generation. It is dozens or hundreds of shots, each potentially from a different engine, reviewed by a different operator, using different prompts, involving different talent licenses. Signing the final MP4 collapses all of that into a single attestation.
This matters for legal review because it allows verification at the granularity where decisions were actually made. "Shot 14 was generated by Kling 3.0, reviewed by operator X at gate B, and uses a licensed likeness from CAST talent Y with royalty attestation Z" is a fundamentally different legal artifact than "this file was made by V8-MOTION."
A V8-MOTION per-shot manifest includes:
Standard C2PA fields: creation tool, creation time, content hash.
Custom assertion: engine name, model version, prompt hash, quality score, gate decisions (A/B/C), operator ID.
Custom assertion: music source, license type, royalty status — per audio track per shot.
When shots are assembled into episodes and features, the assembly itself is recorded — which shots, in which order, with which transitions and grading. The chain is tamper-evident at every level.
Before distributing AI content, you need to answer "what is this and where did it come from?" to platforms, advertisers, and audiences. C2PA gives you an artifact, not a claim.
EU AI Act Article 50 requires disclosure of AI-generated content. US states are passing their own. A signed manifest is stronger evidence than an internal process document.
Healthcare, financial services, education — any industry where content provenance is auditable. Per-shot manifests create an audit trail that survives downstream editing.
If your AI video goes to TikTok, YouTube, or streaming platforms, provenance becomes your proof of rights. Platforms are beginning to require or prefer provenance-tagged content.
V8-MOTION signs a C2PA manifest at the individual shot level — not just on the final export. Every shot in every episode carries its own manifest with engine, prompt hash, operator, gate decisions, and any talent license attestations.
When shots are assembled into episodes (up to 10 minutes) and features (up to 2 hours), the manifests compose. The final exported file's provenance is the verifiable aggregation of every shot's history.
This is not a bolt-on. Provenance is generated as part of the production pipeline — the same pipeline that handles casting, storyboarding, rendering, audio mixing, grading, and distribution. It does not require a separate step or a separate tool.
From script to certified master. Every shot signed. Every chain verifiable.