Catalog scope
Which songs, recordings, versions and release periods are being discussed, and which materials stay outside the review.
RIGHTS WORKSPACE
When the music, release path, rights notes and reporting materials begin to resolve, ERC organizes them into a read-only rights workspace for teams and private partners.
What it is
The rights workspace is not a public backend or an automated file system. It is a way to organize the music identity, rights notes, reporting sources and unresolved questions into one readable file.
It usually appears after the release context is initially clear, helping teams, rightsholders and private partners read from the same facts.
What the workspace holds
This layer brings music identity, reporting sources, rights notes and open questions into one rights-reading structure.
Work identity
Artist credit, release title, platform links, identifiers and the current stage of the music are kept in one readable file.
Rights chain
Master, publishing, producer-side participation and counterparty notes are separated before any partner conversation becomes specific.
Royalty statements
Statement sources, periods, matching status and missing reporting windows are recorded as context, not as public performance claims.
Split and contract notes
Known split sheets, contract boundaries, consent status and unresolved terms stay attached to the file.
Open gaps
The workspace keeps the missing items visible so the next review starts from evidence instead of memory.
How the file is read
A good rights file does not compress everything into a conclusion. It keeps known facts, open questions and the next reading step separate.
01 / Evidence
What is already readable
The file shows the music identity, rights notes, reporting source and current material state before any private follow-up.
02 / Questions
What still needs confirmation
Unclear splits, missing statements, counterparty permissions and version-level questions are kept as open notes.
03 / Next read
Where the memo can continue
Only after the file is coherent does it become useful for a Capital Memo, partner review or a separate rights discussion.
How it connects to Capital Memo
The workspace makes the materials readable first. The Capital Memo appears later, when those materials can support private partner context.
The workspace is the material layer
It organizes source materials, rights notes and reporting context so the project can be read without turning the page into an application form.
Capital Memo is the later reading layer
The memo appears only when the file is clear enough for private partner context; it is not the starting point for release or rights cleanup.
Review Path
The workspace organizes music, contracts, statements, splits and gaps into a file order that can support follow-up review.
Document order first
The workspace starts by putting source materials, rights notes and reporting context into a readable order.
Partner context next
Once the file is clear, the next conversation can focus on partner fit, missing documents and reporting cadence.
Make the file readable.
If the project is still before release, start with the music submission. If the music, rights and reporting materials are formed, continue into the Capital Memo context.
The next step continues from confirmed project context, document needs and partner fit.