Skip to content

iveamm/otari-radar-showcase

Repository files navigation

Otari Radar

Stage: In Development Scope: Released Tracks Focus: Music Rights Risk Output: Readable Audit Report

Otari Radar is a music rights-risk audit platform for released tracks.

It turns a public music link into a readable audit summary that helps reviewers understand:

  • what public metadata supports the track,
  • what rights information is missing,
  • what still needs manual confirmation,
  • and what documents may be required before stronger clearance review.

Otari Radar does not prove ownership, does not register rights, and does not replace legal clearance.

Otari Radar Product Overview


The Problem

Released music can look complete on the surface while the rights picture is still fragmented.

A track may already have a title, artist, album, artwork, duration, public link, and recording identifiers.

But the review can still be blocked by missing or unclear information around:

  • writers and composers,
  • publisher administration,
  • ownership or authority signals,
  • work identifiers,
  • related catalog versions,
  • required rights documents.

Otari Radar Core Problem


What Otari Radar Does

Otari Radar reviews public metadata signals and organizes them into a readable rights-risk report.

Area What It Helps Identify
Track Identity Released track, artist, album, artwork, duration, public link, and identifiers
Recording Metadata Whether public recording metadata supports the reviewed track
Credits & Contributors Writers, composers, performers, producers, technical roles, and business references
Rights Review Missing composition, publisher, ownership, or authority data
Catalog Context Related versions, remixes, covers, weak matches, and catalog notes
Data Quality Completeness, confidence, warnings, and limitations
Actions & Documents Required documents, blockers, key findings, and next action

Audit Response Overview

The audit response is structured so a reviewer can quickly answer:

  • What track is being reviewed?
  • What public data supports it?
  • What information is missing?
  • What still needs confirmation?
  • What documents may be required?
  • What action should happen next?

Otari Radar Audit Response Overview


Example Review Outcome

Field Example
Decision Rights review required
Risk Level Moderate
Readiness Score 33
Track Identity Partially supported
Recording Metadata Supported
Composition Status Review required
Publisher Status Needs confirmation
Ownership Status Not confirmed
Next Action Request missing rights documents

How The Review Works

Step Layer Purpose
1 Input Review Start from a public released track link
2 Identity Resolution Identify the track being reviewed
3 Metadata Analysis Check whether public metadata supports the track identity
4 Credits Mapping Organize contributors and roles
5 Rights Gap Review Highlight missing publishing, ownership, or authority data
6 Catalog Context Review related versions without treating them as automatic conflicts
7 Decision Guard Prevent weak signals from being treated as final clearance
8 Readable Report Produce decision, risk level, blockers, documents, and next action

Why It Matters

Question Why It Matters
Is the released track identity supported? Helps confirm whether the reviewed track matches the intended public release
Is recording metadata consistent enough for review? Separates stronger metadata signals from weak or incomplete signals
Are writer or contributor details incomplete? Reveals gaps that may affect publishing and rights administration
Does publisher information need confirmation? Prevents weak references from being treated as confirmed rights data
Is ownership or administration authority missing? Shows whether manual documentation is still required
Are related versions present? Helps review remixes, covers, sped-up versions, or weak matches as catalog context
What documents are needed before clearance? Converts rights gaps into practical next actions

Sample Output

A simplified public sample is available here:

SAMPLE_REPORT.json

The sample shows the type of decision fields Otari Radar can return in a public-facing audit summary.


Showcase Files

File Purpose
ARCHITECTURE.md High-level layered architecture
DATA_FLOW.md How a released track moves from input to report
DECISION_FLOW.md Decision guard and review logic overview
REPORT_STRUCTURE.md Recommended report organization
TRUST_MODEL.md How public signals are separated from confirmed authority
ROADMAP.md Showcase and product roadmap
NOTICE.md Public repository and proprietary software notice
SAMPLE_REPORT.json Simplified example output

Repository Scope

This repository is a public showcase and documentation repository only.

It does not include source code, credentials, private APIs, provider integrations, scoring rules, decision logic, database schema, or production infrastructure details.

For ownership and usage limitations, see NOTICE.md.


Feedback & Suggestions

Feedback is welcome.

Use GitHub Discussions to suggest improvements, ask questions, or share thoughts about the public showcase.

Useful feedback includes:

  • report structure suggestions,
  • documentation improvements,
  • product presentation ideas,
  • music-rights workflow questions,
  • metadata and audit readability suggestions.

Important Note

Otari Radar is a rights-risk review tool.

It can help organize public metadata, highlight missing information, and guide manual review.

It does not prove ownership, does not register rights, and does not replace legal clearance.

Final clearance still requires confirmation from the relevant rights holders, publishers, administrators, labels, or official authority sources.

About

Public showcase for Otari Radar - a music rights-risk audit platform for released tracks, metadata review, credits, publisher gaps, ownership signals, and required documents.

Topics

Resources

Contributing

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors