Digital Music Rights and Royalty Disambiguation Matrix

Role: Lead Entertainment Rights & Royalties Data Strategist with expertise in music publishing registries and global DSP reconciliation.

Context

• Digital Streaming Source: {{dsp_platform_name}}
• Rights Registries: {{rights_organization_sources}}
• Unmatched Acceptance Target: {{unmatched_threshold_percentage}}
• Audio Fingerprint Score Floor: {{audio_fingerprint_confidence}}
• Contributor Resolution Rules: {{artist_disambiguation_rules}}
• Distribution Settlement Frequency: {{royalty_accounting_cycle}}

Task

Develop an enterprise-grade data cleaning and rights disambiguation framework to ingest, clean, match, and reconcile fragmented track usage logs from {{dsp_platform_name}} against {{rights_organization_sources}}, ensuring unallocated royalties are reduced below {{unmatched_threshold_percentage}} for the upcoming {{royalty_accounting_cycle}}.

Method

1. Design intake profiling checks for {{dsp_platform_name}} streaming files to flag null identifiers, truncated strings, and non-standard currency or play-count fields.
2. Establish an alphanumeric sanitization pipeline for standard industry codes (ISRC, ISWC, UPC, and ISNI), stripping invalid punctuation, spaces, and checksum failures.
3. Create a multi-tiered matching cascade prioritizing exact ISRC/ISWC pairs, followed by normalized title and contributor string matches.
4. Build a fuzzy string matching layer incorporating {{artist_disambiguation_rules}} to parse featured artists, remixers, and alternative track titles.
5. Integrate acoustic fingerprint confirmation rules utilizing {{audio_fingerprint_confidence}} to validate fuzzy matches against audio master registries.
6. Formulate mathematical validation routines to detect and flag royalty split percentages that do not sum to exactly 100.000% across master and publishing shares.
7. Construct a blackbox quarantine workflow for conflicted claims, managing historical re-processing for each {{royalty_accounting_cycle}}.

Constraints

• MUST enforce strict 100% split balance verification; any split mismatch MUST be routed to manual dispute holds.
• MUST NOT overwrite original DSP transaction IDs during canonical mapping and reconciliation.
• Cleaning rules MUST isolate mechanical rights from performance rights allocations before running split validation.
• Fuzzy matching confidence MUST never bypass automated quarantine without secondary fingerprint verification.

Output format

Structure the framework across these specific sections:

1. Code & Identifier Cleansing Pipeline (ISRC/ISWC/ISNI validation rules)
2. Cascading Track & Work Matching Protocol (ordered resolution hierarchy)
3. Split-Sheet Mathematical Reconciliation Model (overclaim/underclaim logic)
4. Unmatched Queue Remediation Workflow (automated reprocessing and dispute triage)
5. Settlement Ready Delivery Schema (validated ledger specifications) Total length must be between 650 and 900 words.

Self-review

• Does the framework account for both recording (master) and composition (publishing) metadata distinctions?
• Are all 6 variables ({{dsp_platform_name}}, {{rights_organization_sources}}, {{unmatched_threshold_percentage}}, {{audio_fingerprint_confidence}}, {{artist_disambiguation_rules}}, {{royalty_accounting_cycle}}) utilized in context?
• Are the mathematical validation constraints explicit regarding 100% split integrity?