Music Rights-Risk Audit Platform for Released Tracks
TrackAudit is a post-release music rights-risk audit platform.
It helps organize the rights picture around an already released track by reviewing available identity information, metadata, credits, publishing signals, ownership or administration information, catalog context, potential conflicts, and missing documentation.
The objective is not to replace authoritative rights records.
The objective is to make a fragmented rights situation easier to understand, review, document, and continue manually.
TrackAudit can help answer questions such as:
- Which released recording is being reviewed?
- Does the available metadata consistently support that recording?
- Which writers, composers, performers, producers, and other contributors can be identified?
- Is publishing information complete enough for the current review?
- Is ownership or administration authority confirmed?
- Are there related versions or conflict signals that deserve attention?
- Which information is still missing?
- Which documents should be requested?
- What should the reviewer do next?
TrackAudit does not treat public metadata as proof of legal ownership or final rights clearance.
This repository is the public product and technical reference for TrackAudit.
It describes what the product does, its review principles, its public scope, and the structure of its user-facing output without exposing the private application implementation.
TrackAudit is available at:
The current product focuses on already released music.
A released track can look complete while the underlying rights picture is still fragmented.
A public music page may already contain:
- a song title,
- artist,
- album,
- artwork,
- duration,
- release information,
- a recording identifier,
- and a public track link.
But that does not necessarily mean the full rights picture is complete.
A review may still encounter:
- an unclear relationship between the recording and musical work,
- missing work identifiers,
- incomplete writer or composer information,
- missing rightsholder information,
- unconfirmed publisher administration,
- unclear ownership or administration authority,
- credits scattered across sources,
- conflicting metadata,
- related versions that require contextual review,
- or missing supporting documents.
TrackAudit organizes these signals into a structured rights-risk review rather than treating a complete-looking release page as a complete rights record.
TrackAudit is relevant to people and teams reviewing rights information around released music, including:
- music publishers and publishing administrators,
- catalog and rights teams,
- labels and distributors,
- metadata operations,
- independent rights holders,
- and technical or research teams working with music-rights information.
| Area | Review Focus |
|---|---|
| Track Identity | Released track, artist, album, duration, artwork, recording identifier, and public identity consistency |
| Recording Information | Available recording metadata and recording-level support |
| Composition Information | Musical-work identifiers, writers, composers, and related rights information |
| Publishing | Available publisher information and whether additional confirmation is required |
| Ownership / Authority | Whether ownership or administration authority appears confirmed, incomplete, or unresolved |
| Credits & Contributors | Writers, composers, performers, producers, technical contributors, and relevant business references |
| Catalog Context | Related versions, remixes, covers, alternate releases, and weaker contextual matches |
| Conflict Signals | Metadata inconsistencies and other signals that may require manual investigation |
| Risk & Data Assessment | Strength, completeness, confidence, and risk meaning of the available information |
| Actions & Documents | Missing documents, review priorities, key findings, and recommended follow-up |
The public TrackAudit workflow can be understood through a small number of review stages:
-
Identify the released track
Establish the recording being reviewed. -
Organize available metadata and credits
Build a clearer picture from the available public information. -
Review recording, composition, publishing, and ownership signals
Separate what appears supported from what still requires confirmation. -
Review catalog and conflict context
Identify related versions and distinguish context from meaningful conflict signals. -
Check authority and documentation gaps
Surface information that requires stronger confirmation. -
Assess risk and apply review guardrails
Avoid presenting incomplete information as final clearance. -
Produce a readable audit result
Explain the current position, missing information, and recommended next action.
For a deeper public description, see:
The TrackAudit result is organized so the reviewer can quickly understand the current rights position before examining deeper details.
A review can include information around:
- track identity,
- credits and contributors,
- catalog and conflict context,
- current decision,
- rights-review status,
- risk and data assessment,
- required documents,
- recommended actions,
- key findings,
- sources,
- and important limitations.
A simplified illustrative example is available in:
The example is intended to demonstrate the type of information a TrackAudit review can communicate. It is not an API schema or representation of the private application contract.
TrackAudit separates two questions:
Is the released recording sufficiently supported for review?
and
Is the available rights information strong enough for a stronger rights conclusion?
Those are not the same question.
A recording may have strong identity and metadata support while publisher administration, ownership authority, contributor identifiers, work information, or supporting documents remain incomplete.
In that situation, TrackAudit keeps the review open rather than interpreting strong public metadata as rights clearance.
See DECISION_FLOW.md.
TrackAudit distinguishes between:
This can help support:
- recording identity,
- metadata consistency,
- contributor discovery,
- catalog context,
- and review prioritization.
Stronger conclusions can require:
- authoritative work information,
- rightsholder confirmation,
- publisher administration confirmation,
- ownership or administration documentation,
- contracts,
- or other authoritative records.
Public information may support a review.
It does not automatically prove ownership.
See TRUST_MODEL.md.
A related public result does not automatically mean that something is wrong.
TrackAudit may encounter:
- remixes,
- covers,
- alternate releases,
- slowed versions,
- sped-up versions,
- alternate recording identifiers,
- and weaker title-based matches.
These can be useful catalog context without constituting a rights conflict.
A stronger conflict conclusion requires stronger supporting evidence.
TrackAudit is live and under active development.
The current product supports a structured post-release workflow across:
- track identification,
- metadata review,
- contributor and credit organization,
- rights-gap review,
- publishing review,
- ownership and authority review,
- catalog context,
- conflict review,
- risk assessment,
- AI-assisted explanation,
- document requirements,
- and readable audit reporting.
See PRODUCT_STATUS.md.
| File | Purpose |
|---|---|
ARCHITECTURE.md |
Public capability model |
DATA_FLOW.md |
Public review flow |
DECISION_FLOW.md |
Decision and review-safety principles |
TRUST_MODEL.md |
Evidence and authority boundaries |
REPORT_STRUCTURE.md |
Human-readable report organization |
SAMPLE_REVIEW.json |
Illustrative public review example |
PRODUCT_STATUS.md |
Current public product scope |
ROADMAP.md |
Public development direction |
CONTRIBUTING.md |
Public feedback guidance |
NOTICE.md |
Repository and proprietary-software notice |
TrackAudit is a rights-risk review tool.
It does not:
- prove legal ownership,
- guarantee global catalog uniqueness,
- register compositions or recordings,
- administer publishing rights,
- collect or distribute royalties,
- replace contracts or authoritative rights records,
- or provide final legal clearance.
Final confirmation may still require relevant rightsholders, publishers, administrators, labels, societies, registries, contracts, or other authoritative sources.
TrackAudit is developed by Otari, a Norway-based music publishing and music-technology project focused on rights, metadata, publishing, and catalog workflows.
This repository intentionally focuses on public product concepts and review behavior.
It does not document the private implementation architecture.
It intentionally excludes:
- application source code,
- internal service structure,
- private processing sequences,
- private API contracts,
- internal field names,
- internal scoring logic,
- decision thresholds,
- provider implementation,
- credentials,
- database design,
- security configuration,
- and production infrastructure.
See NOTICE.md.
Public feedback on product presentation, report readability, rights-workflow clarity, and documentation is welcome.
See CONTRIBUTING.md.