What to provide
Asset formats, creation and editing steps, delivery channels, signer identity, privacy boundaries, and current evidence.
What you will get
A readiness matrix, signing and verification workflow, trust questions, test plan, and implementation scope.
Example: Fictional example: A training-video team wants viewers to inspect how an AI-assisted MP4 was created, but has not selected a production signer.
Copy the full prompt
Customize the bracketed fields.
Use approved business information and have a person review the result before acting.
Help me plan Content Credentials using the C2PA standard for this AI media workflow.
Media types and formats: [image, video, audio, or other verified formats]
Creation and editing steps: [tools, renders, exports, and transformations]
Where people receive the final asset: [download, website, app, social platform, or other]
What provenance we intend to state: [source, AI use, edits, organization, or other]
Signer identity and credential status: [confirmed facts only; never include private keys]
Privacy, consent, and rights boundaries: [rules]
Current code, hosting, and release process: [verified details]
First explain what Content Credentials can and cannot establish: they can make signed provenance tamper-evident, but they do not prove that the content is true, accurate, licensed, or approved. Ask up to five questions that change the implementation. Map the asset from source through editing, final export, signing, storage, delivery, and viewer verification. Identify transformations that may remove or invalidate credentials. Produce a readiness matrix separating documented, implemented, tested, and publicly trusted states. Recommend a small synthetic pilot, a code and workflow integration outline, signing-certificate and key-custody questions, validation checks for trusted, untrusted, missing, altered, and failed-signing assets, and a human review and release gate. Verify current SDK support, trust-list rules, conformance requirements, and provider costs using official sources. Mark unknowns [TO CONFIRM]. Do not request secrets, generate keys, enroll with a provider, certify conformance, sign real assets, or deploy.
Response requirements:
- Begin with a short summary of the goal, confirmed facts, assumptions, and missing information.
- Ask focused clarification questions before completing the work when a missing answer would materially change the result.
- Use clear headings, tables, checklists, or numbered steps where they make the output easier to use.
- Keep source facts separate from recommendations. Quote or cite supplied evidence when the task depends on source material.
- Mark unsupported details, decisions, owners, dates, costs, credentials, and commitments as [TO CONFIRM].
- Identify the three most important risks, failure conditions, or quality checks.
- End with a practical next-action checklist that names the responsible role and the evidence needed to confirm completion.
- Include a final self-review: check the answer against this prompt, list any unmet requirement, and correct it before responding.
- Do not claim that you accessed a system, verified an external fact, completed an action, or tested the result unless evidence in this conversation proves it.Version 1.0 · Updated 2026-10-10 · Free starter template. Evaluate the output in your approved environment.