Creator/Media Inventory

The real problem: inventory presence is not usage clearance

A media library contains an original product image, an AI-retouched derivative, and a cropped social version. One has a release reference, one has provenance but no campaign clearance, and another carries an old rights note. A filename + thumbnail + creator-name inventory can easily reuse the right file in the wrong rights context.

This lesson produces Creator Media Rights-Aware Inventory v1. It does not infer ownership; it separates identity, provenance, rights evidence, and assignment-specific use so missing evidence cannot hide behind a green badge.

Owned boundary

COM-024 owns media inventory and asset/use clearance state. COM-023 owns assignment workflow; COM-025 owns ad release/disclosure/brand-safety gating. This lesson does not publish media or provide universal legal advice.

Core rule: INVENTORIED != CLEARED_BOUNDED. Creator metadata, Content Credentials, or an old license record are evidence slices, not blanket permission.

Mental model: keep four layers separate

1. Asset identity: asset_id + asset_version + content_digest + derivative_of identify the exact asset/version.
2. People & provenance: creator/contributor/source/provenance record origin and history.
3. Rights evidence: copyright owner, usage terms, license, and releases record available rights evidence.
4. Assignment clearance: territory + channel + usage window + assignment determine whether this specific use is cleared.

Completeness of one layer never proves another.

Separate FACT, INFERENCE, and DESIGN

FACT — IPTC: Photo Metadata Standard 2025.1 defines creator/contributor and rights-related fields such as Copyright Owner and Rights Usage Terms, and notes that rights metadata can be affected by laws and contracts.

FACT — C2PA: Content Credentials record tamper-evident provenance/history. The current C2PA specification is 2.4, but verified provenance is not a legal or moral verdict.

INFERENCE: Because digest/version, provenance, and rights can change independently, a safe inventory does not collapse them into one ambiguous field.

MAKNOW DESIGN: INVENTORIED / RIGHTS_UNKNOWN / RIGHTS_RESTRICTED / CLEARED_BOUNDED / EXPIRED / DISPUTED are bounded decision states.

The 21-dimension inventory contract

1) asset_id and asset_version

Separate logical asset identity from version. A crop, retouch, or export can create a new version even when the subject is unchanged.

2) content_digest

A digest binds the review to exact bytes. Dropping the digest and merging derivatives creates identity ambiguity; earlier clearance must not silently migrate.

3) Creator is not contributor is not owner

Keep creator_ids and contributor_roles separate. Photographer, retoucher, AI operator, stylist, or agency roles do not automatically determine copyright ownership.

4) provenance_ref is not permission

C2PA/Content Credentials can strengthen history and linkage but do not replace license scope or campaign-specific releases.

5) Owner, notice, and terms differ

Do not merge copyright_owner, copyright_notice, and rights_usage_terms. They answer different questions.

6) license_ref and release_refs

License and model/property/location releases may have different scopes. Missing decisive evidence should produce RIGHTS_UNKNOWN, not optimistic clearance.

7) Territory, channel, window

Clearance is bounded: where, through which channel, and until when. EU + PAID_SOCIAL + 2026-Q4 is not equivalent to US + ORGANIC + 2026-Q2.

8) Assignment linkage

assignment_refs record where the asset was previously evaluated. History is evidence, not an oracle.

9) derivative_of

Preserve derivative lineage. A crop or AI retouch can inherit history while still requiring rights review for the changed use/version.

10) Verification state

Missing decisive evidence -> RIGHTS_UNKNOWN; scope mismatch -> RIGHTS_RESTRICTED; expired window -> EXPIRED; conflict -> DISPUTED; only complete current scope -> CLEARED_BOUNDED.

Worked examples

1. Complete baseline -> CLEARED_BOUNDED

Version/digest, people, provenance, owner/terms/license/releases and current territory/channel/window all align with the assignment.

2. Asset present, license/release incomplete -> RIGHTS_UNKNOWN

DAM presence or thumbnail availability creates no new permission.

3. Organic rights, paid use -> RIGHTS_RESTRICTED

Same asset, changed use scope; earlier clearance cannot be copied.

4. Usage window expired -> EXPIRED

Intact metadata does not renew permission.

5. Two derivatives merged without reliable digest -> DISPUTED

Resolve identity before any positive rights state.

6. Strong provenance, missing release -> RIGHTS_UNKNOWN

A valid content history can coexist with insufficient use-rights evidence.

Common failure modes

• treating creator as copyright owner;
• treating provenance as permission;
• merging derivatives without version/digest;
• using stale rights notes as licenses;
• dropping territory/channel/window from clearance;
• assuming original releases automatically cover derivatives;
• treating a prior assignment as blanket approval;
• coercing UNKNOWN or DISPUTED into success;
• reusing after expiry without renewal;
• overwriting old decision evidence during transfer.

Alternatives and trade-offs

Folder + filename: low overhead, weak auditability.

DAM metadata-only: better search, but can create false confidence when version/digest and assignment-specific rights are not separate.

Provenance-only: stronger history, no proof of permission.

Rights-aware inventory: more data/review overhead, but failures become local and asset identity can remain stable while use clearance is recomputed.

Experienced bridge: 15 critical questions

What is the asset ID? Version? Digest? Creators? Contributor roles? Provenance ref? Copyright owner? Usage terms? License ref? Release refs? Territory? Channel? Usage window? Verification state? Can evidence_ref reproduce the decision?

Guided and independent practice

The offline lab has eight fixtures: cleared baseline, identity-only inventory, missing rights evidence, territory mismatch, channel mismatch, expired window, derivative/digest dispute, and resolved transfer.

Independent task: move the baseline asset—without changing its bytes—to a new territory and paid channel after the old window. Preserve identity; recompute only changed rights evidence/state. Explain why the earlier CLEARED_BOUNDED label is not the oracle.

Acceptable evidence

Populate all 21 dimensions or preserve an explicit non-success state. Positive clearance without content_digest + provenance_ref + copyright_owner + rights_usage_terms + license_ref + release_refs + territory + channel_scope + usage_window + evidence_ref is not allowed.

The lab is fully synthetic/offline; no live DAM, customer asset, credential, or legal determination is required.

Assessment and transfer

You must be able to: separate COM-024 from adjacent lessons; separate asset from people identity; avoid treating provenance as rights; trace owner/notice/terms/license/releases independently; enforce territory/channel/window; preserve derivative lineage without blanket rights; keep non-success states fail-closed; and recompute changed-use transfer without copying the baseline verdict.

References and freshness

• IPTC Photo Metadata Standard 2025.1 — rechecked 2026-09-15; supports creator/contributor and rights-related metadata, with rights values subject to applicable laws/contracts. Metadata is not permission.
• C2PA Specifications 2.4 / Guiding Principles — rechecked 2026-09-15; Content Credentials capture verifiable/tamper-evident provenance/history without making value judgments or granting use rights.
• Dimension separation, state vocabulary, and assignment-specific clearance are MAKNOW DESIGN.