briefs: LABELTON — A rights primitive for music on-chain

[Pattermesh]

Summary

Position brief cross-posted from kcolbchain/muzix#49. Adapted to the brief format (Abstract + companion-code header), otherwise the canonical text.

Why this brief sits in the research repo

Music finance is a focus area listed in the README (under Payments & stablecoins and RWA tokenisation). LABELTON is the rights-primitive contract we shipped to kcolbchain/muzix in #48; the brief documents the design rationale for builders and researchers outside the muzix codebase.

What it claims

• Prior Web3 music waves (Royal, Audius, Opulous, Sound, Catalog) shipped products on top of an implicit rights model — never the rights primitive itself.
• The music industry's existing legal identifier system (ISRC, UPC, ISWC, IPI) is the legal-system primary-key layer that on-chain music has mostly ignored.
• The LABELTON primitive: a music token whose root mint at master generation lands at a fixed cap-table defined in the same transaction, with the legal identifiers anchored on-chain and off-chain dossiers hash-bound.
• Two architectural choices worth claiming: ERC-1155 supply equals basis-point share (no parallel cap-table mapping), and a standalone owner-gated registry pattern (LABELTON does not extend MuzixCatalog).
• The Muzix DAO / LABELTON product / CR8 chain stratification, with the "DAO sits above, not inside" anti-pattern claim.

What it does NOT claim

• That LABELTON is the only valid design (the open-questions section enumerates five live design debates).
• That the chain identity is decided (CR8 own-L1 vs LUX-subnet is open, tracked in muzix#47).
• That MUSD survives the tokenomics rebrainstorm (open).

Co-byline

@abhicris is co-author by default. Adjust on review if a different framing is wanted.

cc @abhicris

[abhicris]

Welcome to kcolbchain, @Pattermesh — glad you're here. 🌱

Here's what happens from this PR:

1. Our automated review looks for obvious issues (tests, secrets, size) within a couple of hours.
2. If it's clean and CI passes, we merge without back-and-forth.
3. If we need changes, we'll leave a specific comment — not a generic nit. Push another commit and we re-review.

While you wait:

• Run the repo's tests locally (see the repo README.md).
• Keep the PR scoped to one concern — bigger PRs land slower.
• Don't commit tokens or .env contents.

What happens after your first merge

• You're listed on https://kcolbchain.com/contributors/ (opt-out anytime via data/contributors-optout.txt).
• At 2+ merged PRs you're a Regular; at 5+ you're a Fellow — Fellows are the pool we invite first for paid research, partner-org gigs, and grant-funded work. Details: https://kcolbchain.com/docs/org-contribution-policy.html
• Looking for what to pick up next? https://kcolbchain.com/invitations/ lists open help-wanted / good-first-issue across every kcolbchain repo.

Thanks for writing the code. We're building this to last.

[abhicris]

Merged — thank you, @Pattermesh. Your first kcolbchain contribution is in. 🎉

A few things that unlocked with this merge:

• You'll appear on https://kcolbchain.com/contributors/ on the next daily rebuild. Opt out anytime via data/contributors-optout.txt on the website repo.
• You're now a Newcomer in the ladder. At 2 merged PRs you're a Regular; at 5+ you're a Fellow — that's the pool we invite first for paid research, partner-org engagements, and grant milestones. Full policy: https://kcolbchain.com/docs/org-contribution-policy.html
• Looking for the next thing to pick up? https://kcolbchain.com/invitations/ is the live list of open help-wanted / good-first-issue across every kcolbchain repo, refreshed daily.

If you want to stay in the loop on what we're shipping: https://kcolbchain.com/ROADMAP.md