01
Rights scope
Title and territory
Bibue for rights teams
Rights move with their context.
Bring title, territory, and language context into one private review path. Nothing is released from a generic import.
Rights introductions are open. Do not send source files by email.
Private rights record
Catalog scope
- Title
- Recorded
- Territories
- Scoped
- Languages
- Scoped
- Release
- Approval required
Title-level clarity
A release starts with the rights record.
The catalog stays private while scope and authority are reviewed.
- Title
- Recorded before release
- Territory
- Explicit availability
- Language
- Separate edition scope
- Agreement
- Written terms required
Operational path
Scope, review, approval, release.
- 01
Rights
Scope recorded
- 02
Intake
Private package
- 03
Review
Decision logged
- 04
Release
Per-title control
Visible operational record
Every release has an accountable trail.
Review ownership, version history, and unpublish control remain explicit.
02
Release record
Approval required
03
Change history
Accountable actions
Begin with the rights context
Introduce the catalog, not the files.
Source intake starts only after organization, agreement, and title-rights approval.