# TrackForge > Music-as-a-Service platform for catalogue management, royalty intelligence, and rights-rating certification TrackForge is a music catalogue intelligence platform built for the catalogue acquisition and rights management industry. It provides independent catalogue verification, royalty recovery intelligence, and blockchain-anchored AAA-D rating certification. - Website: https://trackforge.studio - Full documentation: https://trackforge.studio/llms-full.txt ## Current Rating Contract - Certificate-facing catalogue and track ratings use the AAA-D scale (current M58 methodology label: v1.1). - Ratings are calculated from run-scoped results-page findings, frozen evidence snapshots, and the original ingested catalogue population, not from mutable cleaned catalogue rows. - Active failure-mode findings are the primary leakage-taxonomy input to the grade. - UK composition sale-diligence inputs also include PRS/SearchWorks WACD agreement binding and ISWC coverage where in scope. - Current M58 scoring applies row risk points for active findings, agreement risk, ISWC risk, and population defects, then applies catalogue-level caps before mapping the final score to AAA-D. - The public M58 v1.1 scoring schedule is exhaustive for rating inputs, row risk points, catalogue caps, thresholds, and recomputation requirements. Source-specific detector recipes and internal discovery heuristics are not public. - Agreement-bound works are explicitly tied to a client PRS/SearchWorks agreement; inferred/unbound works may still generate revenue but carry higher dispute and sale-diligence risk. - Current direct certification scope: United Kingdom and United States. Global society expansion is roadmap until implemented, versioned, and anchored. - Legacy Gold/Silver/Bronze/Declared medal fields may still appear in historical records and compatibility APIs, but they are not the current certificate-facing rating scale. ## Current M58 Proof Bundle The current M58 proof ZIP contains `README.md`, `manifest.json`, `methodology/methodology.json`, `proof/rating_event_proof.json`, `proof/rating_event.json`, `proof/leakage_vector.json`, and `proof/snapshot_links.json`. The rating event must pin the methodology version/hash, taxonomy version, workflow version, jurisdictional scope, subject and snapshot run IDs, rating input hash, leakage-vector hash, Merkle root, OpenTimestamps proof state, and snapshot time. Proof status must be read literally: pending is pending, confirmed is confirmed, failed is failed, and local-only is not a public blockchain confirmation. ## Main Site - [Home](https://trackforge.studio/): Platform overview and capabilities - [Why TrackForge](https://trackforge.studio/why): The case for independent catalogue verification — market failure analysis, information asymmetry, and the Arthur Andersen principle - [The Black Box Problem](https://trackforge.studio/black-box): Why music catalogue valuations need independent verification infrastructure - [ISRC Lookup](https://trackforge.studio/isrc-lookup): Free ISRC lookup tool. Cross-reference any 12-character ISRC across Spotify, MusicBrainz, and The MLC in seconds to surface metadata conflicts, missing registrations, and trapped mechanical royalties. Single and batch modes, CSV/PDF export, no account required. - [MCP server for AI assistants](https://trackforge.studio/mcp): TrackForge's free MCP server lets an AI assistant check a catalogue of recordings against The MLC (up to 50 ISRCs a request: which have no linked work and which have an unclaimed share), look up one song's ISWCs, songwriters and publishers (ISRC lookup, Spotify link or title), and validate a CWR file before it is sent. What it does, example questions and answers, and how to add it to any assistant. No account required. - [Free CWR tools](https://trackforge.studio/cwr-tool): Create Common Works Registration 2.1 files, check and read existing .V21 files, and understand society ACK responses in one free browser workbench. - [CWR Workbench](https://trackforge.studio/cwr-tool/workbench): Start with one of four tasks — Create, Check, Read, or Society response - [CWR problems and fixes](https://trackforge.studio/docs/cwr/problems-and-fixes): Plain-English explanations for every public CWR Workbench check - [CWR glossary](https://trackforge.studio/docs/cwr/glossary): Definitions of Common Works Registration terms - [What each society requires](https://trackforge.studio/docs/cwr/society-requirements): Recipient policies that sit outside the CWR file-format checks - [CWR updates and roadmap](https://trackforge.studio/cwr-tool/updates): Dated releases plus Available now, In development, and Exploring states - [Sample Report](https://trackforge.studio/sample-report): Example MISI (Music Intelligence & Strategic Insight) report - [Terms of Service](https://trackforge.studio/terms) - [Privacy Policy](https://trackforge.studio/privacy) - [Support](https://trackforge.studio/support): What the free tools and MCP server are, how to read their answers, and who to contact (hello@trackforge.studio for questions and help; privacy@trackforge.studio for personal data and report requests; legal@trackforge.studio for terms, legal notices and abuse) ## CWR Workbench The TrackForge Common Works Registration (CWR) Workbench helps publishers and rights administrators create a CWR 2.1 file, check or read an existing .V21 file, and understand a society acknowledgement response (ACK). ### Available features - Create Common Works Registration 2.1 .V21 files from a form or CSV. - Check existing .V21 files for structural, field, share and available destination-profile problems. - Read works, writers, publishers and rights shares from an existing .V21 file. - Understand society acknowledgement responses (ACKs) by accepted, rejected and attention-needed outcome. - Open supported .V21 files in the editor, correct identified issues and download a regenerated file without changing the original upload. - Use plain-language issue explanations with technical evidence kept available under Technical details. - Use all four public tasks without creating an account. - Convert a completed LyricFind spreadsheet into LyricFind’s lyric-1.2 lyrics file or its preferred ownership-1.4 file with ownership and lyrics together, with a review list of rows to fix and values to confirm; uploads are converted and then discarded, never stored. ### Destination submission requirements These recipient policies sit outside the CWR file-format checks and must be confirmed before submission. #### CAPASSO Africa If a work includes a sub-publisher or publishing administrator, CAPASSO accepts that party only when it is directly affiliated with, or linked to, CAPASSO. Confirm the relationship before submission. TrackForge can validate the CWR publisher chain but cannot verify that external relationship from the file alone. ### Roadmap #### Available now Implemented in the public Workbench and backed by a dated release entry. - **Create, check, read and understand responses** — Four outcome-led public tasks cover CWR 2.1 generation, .V21 checking and reading, and society acknowledgement-response review. - **Correct supported .V21 files in the Workbench** — Check a file, open supported content as a pre-filled draft, correct identified issues and regenerate without changing the original upload. Lossy imports stop with preservation blockers. - **Society-led CWR generation choices** — Choose familiar destinations including The MLC, PRS for Music / MCPS via ICE, CMRRA, CAPASSO Africa, AllTrack Worldwide, AllTrack US-only, SACEM, SIAE and SGAE. TrackForge states whether it applies recipient-specific checks or the common CISAC Base CWR 2.1 rules. - **LyricFind lyrics files** — Turn a completed LyricFind spreadsheet into the lyric-1.2 lyrics file or LyricFind’s preferred ownership-1.4 file with ownership and lyrics together, with a review list of rows to fix and values to confirm. Uploads are converted and then discarded, never stored. #### In development Actively being implemented, without an unowned delivery date. Nothing is publicly committed to active development right now. #### Exploring A direction under consideration, not a delivery promise. - **Additional recipient-specific checking** — Further destination rules will move forward as current technical guidance and recipient evidence are verified. Direct GEMA generation also depends on CWR 2.2 support because GEMA currently requires that version. - **Public integration access** — A governed way to integrate Workbench capabilities with other systems is being considered. No public API, webhook contract or delivery date is promised. ### Limits - The Workbench does not submit files to a collecting society or promise that a recipient will accept them. - Public generation and checking support Common Works Registration 2.1 Revision 8 and .V21 files; CWR 2.2 is not available. - CWR 2.1 generation is available for CISAC Base, The MLC, CMRRA, AllTrack Worldwide, AllTrack US-only, CAPASSO Africa, PRS for Music / MCPS via ICE, SACEM, SIAE and SGAE. A separate PRS-specific checking profile remains available for uploaded files. - The MLC, SACEM, SIAE and SGAE choices currently use CISAC Base CWR 2.1 checks; TrackForge does not yet assess every requirement specific to those organisations. - GEMA currently requires CWR 2.2 for direct CWR submissions, so the CWR 2.1 generator cannot create a direct-GEMA-ready file. - Receiver 000 means multiple or unspecified recipients. Under CISAC Base it does not claim that any named society’s destination-specific requirements were assessed. - Additional society profiles and public integration access remain exploratory until implementation and evidence exist. - The LyricFind lyrics file is not sent to LyricFind: you add your LyricFind login and upload it yourself. ## Research & Analysis - [The Unclaimed Economy](https://trackforge.studio/research/unclaimed-economy): 4.25M works with unclaimed US mechanical royalties at the MLC — cross-referenced against 12 data sources - [How ISRC Registration Gaps Cost Labels Money](https://trackforge.studio/research/isrc-registration-gaps): 94.7% Spotify coverage vs 50% MLC work registration — the 45-point gap where $569.9M in mechanical royalties disappear - [Where the Money Goes: A Map of Royalty Leakage](https://trackforge.studio/research/royalty-leakage-map): 12 lifecycle stages where music royalties disappear — 160+ failure modes mapped across 15 data sources - [Where the Money Goes (.md)](https://trackforge.studio/research/royalty-leakage-map.md): Machine-readable markdown version - [Rowntree v PRS: The £3 Line](https://trackforge.studio/research/rowntree-v-prs): Why the Court of Appeal held black box royalties cannot be litigated back, the £3 manual-matching floor the judgment revealed, and what actually works instead - [Rowntree v PRS (.md)](https://trackforge.studio/research/rowntree-v-prs.md): Machine-readable markdown version ## CWR Documentation - [What is CWR?](https://trackforge.studio/docs/cwr/): Complete guide to Common Works Registration format, workflow, ownership vs. collection shares, CWR 2.1 vs 2.2 - [CWR Record Types](https://trackforge.studio/docs/cwr/record-types): Reference for all CWR record types — NWR, REV, SPU, SPT, SWR, SWT, PWR, HDR, GRH, GRT, TRL - [CWR problems and fixes](https://trackforge.studio/docs/cwr/problems-and-fixes): Every problem the CWR Workbench can report, why it matters and how to fix it ## Certification Documentation — Overview - [Why TrackForge](https://trackforge.studio/docs/certification/overview/why-trackforge): Why the music industry needs independent metadata verification - [The Problem](https://trackforge.studio/docs/certification/overview/the-problem): Structural issues in music metadata and rights management - [The Market](https://trackforge.studio/docs/certification/overview/the-market): Catalogue acquisition market context and due diligence gaps - [The Solution](https://trackforge.studio/docs/certification/overview/the-solution): How TrackForge addresses metadata verification - [Independent Verification](https://trackforge.studio/docs/certification/overview/independent-verification-explained): What independent verification means in practice - [What is Certification?](https://trackforge.studio/docs/certification/overview/what-is-certification): TrackForge AAA-D rating certification, evidence snapshots, proof bundles, and remediation flow - [Scope](https://trackforge.studio/docs/certification/overview/scope): What certification does and does not cover - [Audience](https://trackforge.studio/docs/certification/overview/audience): Who certification is designed for - [Getting Started](https://trackforge.studio/docs/certification/overview/logging-in): How to access the platform ## Certification Documentation — Methodology - [Rating Methodology (AAA-D)](https://trackforge.studio/docs/certification/methodology/golden-record-selection): Current methodology v1.1 scoring recipe, leakage-taxonomy findings, risk points, catalogue caps, agreement binding, and ISWC coverage - [Rating Input & Scoring Schedule](https://trackforge.studio/docs/certification/methodology/rating-input-scoring-schedule): Public M58 v1.1 scoring contract for rating inputs, row risk points, catalogue caps, AAA-D thresholds, and independent recomputation - [Value Chain Maturity Model](https://trackforge.studio/docs/certification/methodology/value-chain-maturity-model): Framework for assessing catalogue metadata maturity - [Enrichment & Validation](https://trackforge.studio/docs/certification/methodology/enrichment-validation): Multi-source enrichment pipeline and conflict resolution - [Canonicalisation](https://trackforge.studio/docs/certification/methodology/canonicalization): Deterministic JSON serialisation for cryptographic hashing - [Hashing](https://trackforge.studio/docs/certification/methodology/hashing): SHA-256 cryptographic hash generation - [Merkle Trees](https://trackforge.studio/docs/certification/methodology/merkle-tree): Binary Merkle tree construction for batch certification - [Blockchain Anchoring](https://trackforge.studio/docs/certification/methodology/blockchain-anchoring): Bitcoin anchoring via OpenTimestamps - [Independent Verification](https://trackforge.studio/docs/certification/methodology/independent-verification): How anyone can independently verify a certificate - [Recertification](https://trackforge.studio/docs/certification/methodology/recertification): When and how certificates are renewed ## Certification Documentation — For Lawyers - [Certification Scope](https://trackforge.studio/docs/certification/for-lawyers/certification-scope): Legal scope and positioning of certification - [Liability & Risk](https://trackforge.studio/docs/certification/for-lawyers/liability-risk): Liability boundaries and risk allocation - [Data Handling & GDPR](https://trackforge.studio/docs/certification/for-lawyers/data-handling-gdpr): Data protection compliance - [Certificate Wording](https://trackforge.studio/docs/certification/for-lawyers/certificate-wording): Legal language used in certificates - [Conflicting Certifications](https://trackforge.studio/docs/certification/for-lawyers/conflicting-certifications): How conflicts between certifications are resolved - [Rating Independence](https://trackforge.studio/docs/certification/for-lawyers/rating-independence): Structural independence of the rating methodology ## Certification Documentation — For Catalogue Owners - [Deliverables](https://trackforge.studio/docs/certification/for-catalogue-owners/deliverables): What you receive with certification - [Reading Your Certificate](https://trackforge.studio/docs/certification/for-catalogue-owners/reading-your-certificate): How to interpret certificate fields - [Verification](https://trackforge.studio/docs/certification/for-catalogue-owners/verification): How to verify your certificate independently - [Proof Bundle](https://trackforge.studio/docs/certification/for-catalogue-owners/proof-bundle): Contents of the cryptographic proof bundle - [Recertification](https://trackforge.studio/docs/certification/for-catalogue-owners/recertification): Keeping your certification current ## Certification Documentation — Technical Reference - [Verification API](https://trackforge.studio/docs/certification/technical/verification-api): API endpoints and schema specifications - [Canonical JSON Schema](https://trackforge.studio/docs/certification/technical/canonical-json-schema): JSON schema for canonical records - [Merkle Proof Format](https://trackforge.studio/docs/certification/technical/merkle-proof-format): Data format for Merkle proofs - [OpenTimestamps](https://trackforge.studio/docs/certification/technical/opentimestamps): OTS file format and verification - [Data Security](https://trackforge.studio/docs/certification/technical/data-security): Security architecture and data handling - [Public MCP Server](https://trackforge.studio/docs/ai-assistants/mcp-server): Connecting an AI assistant or any MCP client to the catalogue registration check (up to 50 ISRCs: MLC registration and unclaimed shares), the song registration check (an ISRC lookup with ISWCs, writers and publishers) and CWR validation; connection settings and the clients tested so far ## Certification Documentation — Reference - [Glossary](https://trackforge.studio/docs/certification/glossary): Key term definitions ## AI Access All public pages serve markdown to AI crawlers via User-Agent content negotiation. You can also append `.md` to any URL: - https://trackforge.studio/why.md - https://trackforge.studio/isrc-lookup.md - https://trackforge.studio/mcp.md - https://trackforge.studio/cwr-tool.md - https://trackforge.studio/cwr-tool/workbench.md - https://trackforge.studio/docs/cwr/problems-and-fixes.md - https://trackforge.studio/docs/cwr/glossary.md - https://trackforge.studio/docs/cwr/society-requirements.md - https://trackforge.studio/cwr-tool/updates.md - https://trackforge.studio/docs/certification/overview/what-is-certification.md - https://trackforge.studio/research/unclaimed-economy.md - https://trackforge.studio/research/isrc-registration-gaps.md - https://trackforge.studio/research/royalty-leakage-map.md - https://trackforge.studio/research/rowntree-v-prs.md The public ISRC lookup is available for automated, unauthenticated use: - API catalogue: https://trackforge.studio/.well-known/api-catalog - OpenAPI description: https://trackforge.studio/.well-known/openapi/isrc-lookup.json - Authentication and rate-limit documentation: https://trackforge.studio/auth.md - Remote MCP server, named TrackForge (no auth; catalogue registration check for up to 50 ISRCs, with MLC registration and unclaimed shares; song registration check by ISRC lookup, with ISWCs, writers and publishers; CWR validation; report requests): https://api.trackforge.studio/api/v1/mcp - MCP server overview, example questions and setup steps: https://trackforge.studio/mcp - MCP server documentation: https://trackforge.studio/docs/ai-assistants/mcp-server ## Optional - [llms-full.txt](https://trackforge.studio/llms-full.txt): Complete documentation content for LLM context