AI Artwork Provenance Sheet for a Mixed-Source Asset Pack

An AI art provenance record should show how each asset entered a mixed-source pack, what changed afterward, which tools or AI systems were involved, and what remains unanswered. It is a source-history document, not a conclusion about ownership, copyright protection, authenticity, completeness, or commercial-use rights.

Keep four evidence groups separate:

• Source history: where the asset came from and what the source terms state.
• Process history: prompts, iterations, human edits, tools, and contributor roles.
• Export evidence: what remains visible or verifiable in the file another system will receive.
• Open questions: rights, licensing, attribution, platform, printer, or format issues requiring separate review.

This separation keeps a polished preview or visible credential from carrying more meaning than the available evidence supports.

What to Record for Each Asset

Use one entry per asset, even when several assets came from the same generation session. A mixed-source pack may include original drawings, licensed elements, AI-assisted images, public-domain material, commissioned work, and later edits. One broad statement rarely describes those differences clearly enough for review.

Field names can change to fit the pack. The distinction between source, process, export, and unresolved questions should remain.

A Usable Provenance Sheet Template

Asset ID:
Pack role:
Current filename:
Current format:
Current version:

Original source:
Source location or reference:
Source terms:
Permission or license record:
Creator information:

AI involvement:
AI tool, model, or feature:
Prompt or instruction history:
Input images or source materials:
Generation dates or session details:
Selected generation:
Known limitations in the generation record:

Human edits:
Sketches or plans made before generation:
Edits after generation:
Compositing or source combinations:
Changes to silhouette, outline, color, texture, or layout:

Other contributors:
Contribution recorded:
Attribution recorded:
Responsibility or authorship question:

Linked evidence:
Evidence reference IDs:
Process files:
Source-term files:
Screenshots or credential views:
Missing evidence:

Export check:
Export filename:
Export format:
Export date:
Application or export path:
What remains visible:
What is absent:
What was inspected:

Unresolved rights questions:
Unresolved source questions:
Unresolved platform or listing questions:
Unresolved production questions:

Review status:
Documented
Shown in export
Inferred from workflow
Unresolved

Apply the final status to individual fields where possible. An asset can have a documented source but an unresolved AI tool history. A visible Content Credentials panel may show creator or tool information while leaving upstream source history incomplete.

Separate Origin, Edits, Tools, and Supporting Records

Provenance standards such as the C2PA Technical Specification offer a useful structure for distinguishing an asset's origin, later actions, tools, and related assertions. For a pack review, ask four separate questions:

• Origin: What entered the workflow first?
• Edits: What actions changed the asset afterward?
• Tools: Which applications, features, or AI systems were used?
• Supporting records: Which files or statements support each entry?

These questions should not collapse into one label such as “AI-generated.” That label may describe part of the process, but it does not describe the complete source history.

For example, an asset might begin as a hand-drawn sketch, pass through an image-generation feature, receive manual repainting, combine with a separately licensed texture, and export as a transparent PNG. Record those stages separately:

Origin: creator sketch retained as a working file.
AI involvement: image-generation feature used for an intermediate variation.
Human edits: silhouette redrawn, facial details replaced, border added.
Additional source: licensed texture combined during compositing.
Export: transparent PNG inspected after export.
Open questions: source terms for the AI service and texture require confirmation.

This records the process without assigning a legal status to the final asset.

Describe AI Assistance Without Assigning the Outcome

Human edits in AI artwork belong in the process record, but a list of edits does not by itself determine authorship or copyrightability. Describe observable actions rather than inserting a legal conclusion.

• Selected one variation from six recorded outputs.
• Repainted the eyes and adjusted the silhouette.
• Removed background elements with a manual mask.
• Combined the generated character with a separately sourced accessory.
• Changed the composition after reviewing the generated preview.
• Created the final lettering independently.
• No prompt or generation history was retained.

Avoid “fully human-created” when the record shows AI assistance. Also avoid treating the AI system as the sole creator when the workflow includes human planning, selection, editing, or compositing. Process evidence helps another reviewer understand development; it does not settle every rights or licensing question.

Distinguish AI Tools Used From AI Involvement

AI tool used identifies the application, model, or feature when known. AI involvement describes the action performed with it.

AI tool used: image-generation feature in a creative application.
AI involvement: produced an intermediate character variation from a text instruction.
Human contribution: selected the variation, redrew the outline, changed the colors, and prepared the sticker border.

When the exact model, feature, or version is unavailable, record that limitation directly:

AI tool used: application recorded; model and feature version unavailable.
AI involvement: inferred from the saved workflow and visible generation history.

Do not fill missing fields with assumptions. “Unknown” is more useful than a complete-looking entry that cannot be checked. Tool use, creator contribution, attribution, responsibility, authorship, copyright, and licensing remain separate questions.

Place Source Terms Beside Source History

A source name alone is not enough for a mixed-source pack. Record the terms that control each external element, along with the date or version when available.

• Source identifier.
• Original creator or provider, if stated.
• Permission, license, commission, or purchase record.
• Uses allowed in the stated terms.
• Restrictions stated in the terms.
• Required attribution.
• Rules concerning modifications.
• Restrictions on redistributing the source file.
• Any missing or ambiguous point.

Keep wording close to the source terms. Do not convert “use permitted under stated conditions” into “commercial use confirmed” until the terms and intended use have been checked separately.

A provenance sheet can show that a source term was reviewed. It cannot settle whether that term applies to every element in the finished pack.

Compare the Record With the Export

Do not stop when the working application displays provenance details. Inspect the exported asset that will enter the pack, listing workflow, or production handoff.

• Exported filename and format.
• Application, export path, and relevant settings.
• Inspection point and date.
• Provenance details that remain visible or verifiable.
• Details that are absent or were not inspected.
• Any later conversion or platform transformation.

Content Credentials can serve as one implementation example for displaying creator, tool, and generative-AI information. Their behavior depends on the application, format, export path, and later platform handling.

There is no universal result here for metadata persistence, export stripping, marketplace ingestion, printer behavior, or cutter behavior. Test the actual workflow or consult current requirements for the specific system involved. The acceptance condition is simple: state what was inspected, and do not describe uninspected information as surviving export.

Use Clear Evidence Status Labels

Documented

The information appears in a retained source, process file, written statement, or source-term record.

Shown in export

The information was inspected in the exported file or its associated display. This describes observation, not rights or authenticity.

Inferred from workflow

The information follows from the recorded sequence but is not directly shown in the final asset. Identify the supporting process file.

Unresolved

The record lacks enough evidence to make the statement more precise.

For example, “manual repainting occurred after the selected generation” may be inferred from a retained process file, while the exact model version may remain unresolved. These labels keep a complete-looking sheet from hiding incomplete evidence.

Common Misreadings

• A provenance record documents source history and process evidence; it does not determine the result of a rights analysis.
• A creator or generative-AI label does not show that the underlying asset is cleared for every intended use. Source terms still require review.
• A visible credential reports what that implementation displays at the inspected point. It does not show that every transformation, contributor, or upstream source appears in the record.
• A polished mockup is preview evidence. It does not show that the source record is complete or that a later platform, printer, or cutter will accept the file.
• Metadata displayed in an application may not remain in the exported file or survive a later conversion. Inspect the file another system will receive.

When to Hand Off the Review

Finish the provenance pass when each asset has:

• A recorded origin or an explicit missing-origin entry.
• Source terms attached or marked unresolved.
• AI involvement described without inflated certainty.
• Human edits and other contributors recorded where known.
• Process evidence identified by stable reference.
• The actual export inspected, or the inspection gap stated.
• Unresolved rights questions separated from process facts.
• Platform, printer, or cutter dependencies left open when current requirements were not checked.

Then hand unresolved rights questions to a separate source-terms or legal review, and check platform or production requirements independently. The sheet is complete when another reviewer can distinguish what is stated, shown, inferred, and still unanswered.