Sovereign Music Hub

Excavationpro — independent of DistroKid, Spotify, and YouTube Music. Every master is identified by SHA-256, not a platform ID. If commercial stores delist a song, the vault still knows the bytes.

Lattice Merkle root

…

This root is the vault’s fingerprint on the LYGO lattice. Recompute after every ingest.

How retrieval works

1. Discover — search this page (titles, ISRCs, hashes).
2. Identify — copy the SHA-256 (true identity of the master).
3. Retrieve — from the steward vault MUSIC_VAULT/cas/… or local gateway http://127.0.0.1:8765/sha256/<hash> when the steward is online.
4. Verify — re-hash the file; it must match. Platforms can rename or vanish; the hash cannot lie.

Vault objects

TitleISRCSizeSHA-256

What the sovereign music hub is

The hub is the workshop view of the catalog: the public streams, the vault, the ledger, and the links that explain how they relate. It is not a second player and not a storefront. It is the place to understand what the catalog is made of before you press play somewhere else.

The vault

The vault holds the archival masters. The public catalog holds the listening copies. Keeping the two separate is the whole rights model: the stream is open, the master is not. The vault is described here so the public catalog can be trusted; it is not a download page.

The public catalog

The catalog is large and curated. New work is added deliberately, not by an infinite upload feed. The ledger records a snapshot of titles, hashes, and metadata; the player at asiancoastline.com does the playing. Use the catalog to verify, the player to listen, and the essays to understand the choices.

Rights and corrections

A free stream is a listening copy, not a sync license or a commercial grant. If you want to use a track in a project, ask first. If a row is wrong or a file is missing, use the contact page with the title and the correction.

How the public view differs

The public hub is a window, not the vault. It shows the shape of the catalog — the streams, the ledger, the rights line — without exposing the archival masters. That separation is what lets the player stay open while the catalog stays owned.

The hub is also a maintenance surface. It links the player, the catalog, and the essays so a reader can move from a track to the context without guessing which page is canonical. If a link is wrong, the contact page is the repair route.

Why keep a separate hub

The player is for listening; the hub is for understanding. Keeping them separate means the player can stay fast and the explanation can stay complete. It also means a change to the catalog does not require redesigning the player.

The public record

The public record is intentionally smaller than the vault. It lists what a listener can reach and what a reader can check; it does not expose the archival files. That is the balance the hub exists to explain: the catalog can be inspected without becoming a file locker, and the master can stay private without making the public page mysterious.

If you are citing the catalog, cite the public hub or the ledger page. If you are listening, use the player. If you are asking for a file, read the license first.

A final note on trust

Trust here is not a badge; it is the ability to check the page against the public record. The hub gives you the links to do that. If a claim cannot be checked, it is not part of the public record yet.