Rights and clearance
No asset moves from concept to release merely because it appears in this repository.
Rights layers
| Layer | Question | Required evidence |
|---|---|---|
| Composition | Who wrote lyrics, melody, and other copyrightable musical material? | Contribution records and signed split sheet |
| Master | Who owns and may exploit the final recording? | Signed production/collaboration agreement and payment record |
| Performance | May each recorded performance be released and edited? | Performer consent and release terms |
| Beat / instrumental | Is the license valid for the intended release, territory, term, and revenue? | License copy and purchase/permission evidence |
| Samples / interpolations | Was third-party material identified and cleared? | Written clearance or documented replacement |
| Voice / likeness | May a name, image, biography, or voice be used publicly? | Specific written consent |
| AI output | What tool generated or transformed what element, under which terms? | Tool/version record, source record, disclosure, and terms review |
| Promotion / case study | May the collaborator and work be discussed publicly? | Separate approval of the named public use |
Track clearance gate
For each track, complete the following before distribution:
- identify every contributor and source asset;
- distinguish pre-existing material from new work;
- complete contribution records and a split sheet totaling 100%;
- define master ownership, licenses, payment triggers, and revenue participation;
- confirm beat, sample, interpolation, and third-party permissions;
- record AI-generated or AI-transformed elements and applicable service terms;
- obtain performer, voice, likeness, credit, and promotional permissions;
- replace any element that cannot be documented;
- approve final credits, metadata, and delivery materials;
- complete the sync/master scope alignment check below before marking any track cleared.
Sync / master scope alignment
Every track requires two independent licenses: a sync license (composition side, from the songwriter or publisher) and a master use license (recording side, from the master owner). Each license is independently scoped. Your effective clearance is the intersection of the two — the most restrictive combination of their terms. A sync license cleared worldwide/perpetuity paired with a master license cleared domestic/five-year leaves you only domestic/five-year.
For each track, complete this table before the track clears the gate. All three dimensions must match across both licenses, and all three must cover the intended release scope before the track is marked cleared.
| Dimension | Sync license grant | Master use license grant | Do they match? | Covers intended release? |
|---|---|---|---|---|
| Media | (e.g. SVOD/subscription streaming, theatrical, home video, promotional) | (same fields) | Yes / No / Pending | Yes / No / Pending |
| Territory | (e.g. worldwide, US only, list of countries) | (same fields) | Yes / No / Pending | Yes / No / Pending |
| Term | (e.g. in perpetuity, 5 years from release, festival-only) | (same fields) | Yes / No / Pending | Yes / No / Pending |
Stop condition: if any cell in the "Do they match?" or "Covers intended release?" columns reads No or Pending, do not proceed to distribution, licensing, or pitching. Resolve the narrower grant first — either by expanding it or replacing the element.
Streaming scope requirement
For any release on a subscription streaming platform (Netflix, Hulu, Max, Disney+, Apple TV+, or equivalent), both the sync and master licenses must explicitly state:
- Media: subscription video-on-demand (SVOD) streaming, and any additional tiers in scope (AVOD, FAST, download-to-own);
- Territory: worldwide (or the full territory of the distribution agreement);
- Term: in perpetuity, or a term that outlasts the distribution agreement.
A license that is silent on streaming does not cover streaming. A license limited to "theatrical and home video" does not cover Netflix. Confirm the express language in the signed document — do not infer coverage from silence or from the rights holder's verbal assurance.
Beat / instrumental license checklist
Most beat-store and Fiverr licenses default to limited scopes that do not cover subscription streaming. Before using any beat or instrumental in a track intended for streaming distribution, confirm the following in the signed license document:
- [ ] License type explicitly permits synchronization in a film or series (not just a music release);
- [ ] Media grant includes subscription streaming / SVOD;
- [ ] Territory is worldwide (or matches the distribution territory);
- [ ] Term is in perpetuity (or outlasts the distribution agreement);
- [ ] Revenue-type restrictions (some licenses exclude streaming revenue or cap it) are reviewed and acceptable;
- [ ] License is for the specific track version (with hook, extended, tagged/untagged) actually used in the recording.
If any item is unchecked, the license must be upgraded, replaced, or the beat element must be replaced before the track clears.
Trailer and promotional use
Sync and master licenses for in-film use do not automatically extend to trailers, teasers, clips, social media excerpts, or advertising. If any track is used in promotional materials, confirm a separate grant or confirm the in-film license expressly covers promotional use.
Charlie J boundary
The Fiverr listing is evidence of a public service offer, not permission to use Charlie's name, voice, likeness, work, or terms outside an accepted order or separate agreement. This repository does not claim that Charlie is attached to the EP. A paid commission and a named public case study are separate decisions.
Suno demo boundary
The existing demo is described as human-authored, AI-generated based on Dominique's stated concept and source-lyrics authorship and Suno's generation of the audible rendition. Before commercial use, preserve the exact generation record, verify the account and plan terms applicable on the generation date, and review every source element. The demo must not be represented as Charlie's performance.
AI disclosure requirement for streaming delivery
Netflix and comparable streamers are increasingly requiring AI warranty language in delivery packages. For any track containing AI-generated or AI-transformed elements, the delivery package must include:
- the name and version of the AI tool used;
- the generation date and account/plan tier active on that date;
- a record of the source prompt or input where applicable;
- a statement confirming the output complies with the service's commercial terms for the intended use;
- a disclosure flag in the track metadata.
This is documented in AI-DISCLOSURE.md. Confirm that file is complete and current before delivery.
Storage
Public GitHub holds only public-safe documentation. Protected storage holds source audio, stems, sessions, agreements, IDs, contact details, receipts, and unpublished work. Public files may refer to a stable private evidence locator but must not expose protected URLs or credentials.
Stop conditions
Do not release, license, pitch as attached talent, train on a contributor, or publish a named case study when required evidence is missing or disputed. Escalate unresolved ownership or contract questions to qualified counsel.
Source: sync/master scope alignment framework informed by Thoolie — Music Clearance for Independent Filmmakers (thoolie.com/creator_resource/music-clearance-independent-filmmakers/, accessed September 13, 2026). This is project-control documentation, not legal advice.
Rule catalog relationship
The proposed docs/architecture/rule-catalog.md operationalizes controls in this file for human review. It does not replace this document or create independent rights requirements.
If the rule catalog, this file, PROJECT-STATUS.md, PROVENANCE.md, or AI-DISCLOSURE.md conflict, implementation stops. Record the contradiction, reconcile the applicable control documents, and only then resume the gate. No control file silently overrides another at runtime.
Download Markdown source · Presentation does not indicate legal review or clearance. See the document's stated status.
PIXIE