Record Setup — the Core Data Record

2.1 What the CDR is for

The Core Data Record is the provenance infrastructure of the CIP framework. Its purpose is to make a creative asset's rights legible — to turn the invisible web of subsisting rights into a structured, machine-readable record that AI systems, platforms, agencies, and lawyers can query and verify.

Without a CDR, a creative asset enters the AI pipeline as a blob of content with no identity. The pipeline cannot know who created it, what rights subsist in it, or on what terms it may be used. With a CDR, every transformation, ingestion, and use event can be recorded and verified. The CDR is to creative content what a ship's manifest is to cargo: it does not create the goods, but it makes their movement accountable.

2.2 Key CDR fields

Asset identification — title, asset type (audio, image, text, video, dataset), format, unique identifier, creation date, version

Creator information — named creator(s), role (composer, performer, photographer, author, producer), jurisdiction, contact rights (the authorised way to reach the rights holder for licensing)

Rights bundle — which of the six CIP rights categories subsist in this specific asset. Status for each: Subsisting / Waived / Assigned / Expired / N/A

Input licence class — how the asset may be used by others:

• Owned — full rights, all transformations permitted to the rights holder
• Licensed (Commercial) — paid usage, scope as agreed
• Licensed (Non-Commercial) — restricted to non-commercial use
• Open (Permissive) — minimal restrictions, free use
• Open (Conditional) — attribution and/or share-alike required
• Restricted — limited use, no derivatives
• Prohibited — no use, opt-out/blocked

Consent framework — whether consent is granted for AI training ingestion, fine-tuning, commercial use; any temporal or scope limits; the consent mechanism

Transformation permissions — Original, Reproduction, Modification, Remix, Style Transfer, Synthesis — each set to Permitted / Attribution-Required / Restricted / Blocked / On-Request

Provenance chain — any prior works, datasets, or sources this asset derives from

Registry ID — the unique Rights Registry identifier assigned at CDR registration, enabling lookup and verification

2.3 Creating your first CDR

CDRs are created through the CIP portal at creativeip.org/portal. The process takes approximately 15 minutes for a straightforward asset.

Step-by-step for a musician creating a CDR for a recorded song:

1. Log in or register at creativeip.org
2. Navigate to CDR Management → New CDR
3. Enter asset details: title, type (Audio), format (MP3/WAV), creation date
4. Enter creator information: full legal name, role (Composer / Performer), jurisdiction
5. Set rights bundle: Expression = Subsisting, Performance = Subsisting, Moral = Subsisting, NILP = Subsisting, Publishing = Subsisting, Biometric = Subsisting
6. Set input licence class: Prohibited (if you do not want AI training use)
7. Set consent framework: Training Ingestion = Not-Granted, Fine-Tuning = Not-Granted
8. Set transformation permissions: Style = Blocked, Reproduction = Blocked, Synthesis = Blocked
9. Connect to Rights Registry → receive your CDR Registry ID
10. Copy the CDR Registry ID to your cip.md file via CIP-CDR-ID