Before Day 1

Bring the Milestone 4 lead candidate, authoritative audio file, lyrics, artwork, prompts or directions, source material, collaborator information, metadata, known rights questions and current intended use. Use the artist name, song title, version, date and record version number on every output.

Day 1 — Identify

Establish the project, authoritative version and intended use

Rights decisions cannot be made for an undefined song, changing version or vague future purpose.

Record: artist, approved and working titles, parent song ID, authoritative filename, location, duration, format, creation date, selection date and release status.

Choose the intended uses: private portfolio, streaming, social, YouTube, monetization, digital or physical sale, Shopify, podcast, live performance, client work, advertising, sync, game, remix, licensing or training example.

List every component requiring evidence: composition, lyrics, vocals, instrumental, uploads, samples, collaborators, artwork, typography, video, metadata and disclosure.

Decision: defined and ready, missing authoritative version, missing essential files, or return to Milestone 4.

Day 2 — Reconstruct

Build the Creation and Version Timeline

Map the project from original idea through lyric drafts, prompt drafts, generations, uploads, selections, extensions, remasters, stem work, collaborator additions, artwork, metadata and master approval.

Use platform dates, filenames, document history, cloud timestamps, messages, email, screenshots, DAW sessions, export dates and receipts. Classify each entry as confirmed, strongly supported, reconstructed, estimated or unknown.

When a date cannot be confirmed, mark it estimated and explain the basis. Never invent precision.

Day 3 — Document

Build the Human Contribution Record

Document actual human work without exaggeration. Cover concept, story, message, audience, original or revised lyrics, pronunciation, translation, prompt design, structure, instrumentation, arrangement, vocal direction, version selection, rejected outputs, extensions, DAW or stem edits, mixing, mastering, artwork direction, metadata, disclosure and final approval.

For every claimed contribution, record the action, date, supporting file, version affected and result.

Use the verified Human Contribution Record Checklist and review the Human + AI Music workflow.

Do not turn contribution evidence into automatic claims of total authorship, sole ownership, originality or legal protection.

Day 4 — Trace

Build the Source and Asset Register

Register every external or separately created element that appears in the final package: uploads, samples, loops, stems, field recordings, collaborator performances, quotations, translations, AI images, photos, stock, fonts, textures, templates, logos, voice material and platform project records.

The key question is not only what entered the project, but what survived into the approved version.

Day 5 — Confirm

Document permissions, collaborators, credits and public claims

For each external asset, record the permission type, licence, rights holder, date, commercial use, modification and redistribution rights, attribution, territory, duration, expiry, prohibited use and stored evidence.

For each collaborator, record legal/professional name, public credit, role, files supplied, fee, payment, split, ownership position, permitted uses, confirmation date and agreement location.

Review public phrases such as “written by,” “produced by,” “composed by,” “performed by,” “original,” “fully human-made,” “AI-assisted,” “exclusive,” “cleared” and “licensed.” Classify each as supported, partly supported, unsupported, requires qualification or should not be used.

A missing essential permission, contributor dispute or unsupported major claim blocks approval.

Day 6 — Assess

Run the rights-risk and intended-use review

Review version traceability, human contribution, AI tool terms and account status, uploads, samples, lyrics, voice and likeness, collaborators, artwork, fonts, metadata, disclosure, ownership wording and the intended platform or commercial use.

Use risk labels: low, moderate, high, unresolved or not applicable. Low risk is not guaranteed clearance; high risk is not an automatic infringement finding.

Choose one decision: approved for private use, approved for public non-commercial use, approved for the stated commercial use, approved with restrictions, revise documentation, replace an element, obtain permission, hold, platform review required or qualified legal review recommended.

Use the verified Rights + Contribution Tracker and consult the Release Router.

Day 7 — Approve

Assemble the Working AI Music Rights and Proof Record

Combine the Project Evidence Inventory, Creation and Version Timeline, Human Contribution Record, Source and Asset Register, Permission and Licence Record, Credit and Collaboration Record, Public Claim Review and Rights Risk Matrix.

Attach the authoritative master, lyrics, artwork, metadata, disclosure, agreements, receipts, unresolved-issue register, approval date, review date and evidence-folder location.

50-point validation

• Project and version traceability — 10
• Human contribution evidence — 10
• Source and permission clarity — 10
• Credits, claims and disclosure — 10
• Intended-use decision and organization — 10

Recommended approval: 35/50, no category below 6, no missing master, critical permission gap, contributor dispute or knowingly unsupported public claim.

Run the AI Track Validation Checklist.

Copy this prompt into ChatGPT

Troubleshooting

Old prompts are missing

Record confirmed evidence, label the gap and preserve remaining files. Do not invent a complete history.

The final file is unclear

Return to Milestone 4 and establish version authority.

A receipt is missing

Attempt recovery and keep the asset unresolved until sufficient evidence exists.

A collaborator agreed verbally

Request written confirmation before important public or commercial use.

Platform terms changed

Record the terms relevant at creation and separately review current requirements for the intended use.

Completion statement

I built a dated evidence record explaining how the release was created, which sources and contributors were involved, which files are approved and what use is currently supported by the available evidence.

Continue to the Member Validation Path