Introducing /receipts — every chain, machine-readable

In the last week, the receipts system on VoxEmpire crossed a threshold. The wedge — every release ships with its rights chain — moved from a promise on the homepage to a discoverable, distributable, portable artifact at every layer of the platform. This post tracks what shipped, why it matters, and what is now possible because of it.

What a "receipt" actually is on VoxEmpire

A rights chain on VoxEmpire is a structured record: contributors, AI tools used (with the part of the work each touched), the time-ranged elements that make up the track or beat, and a signed warranty. Stored as data, rendered as a receipt page, exported as JSON, and indexed as schema.org structured data. Not a sticker. Not a marketing claim. The actual record.

What shipped

Every BHM track now has a real chain

All 13 founding tracks on the Brutally Honest Music catalog have documented chains. Open any one at /receipt/<slug> and you see the full ledger — intro, verses, choruses, optional bridge, outro — each with its source, status (original, AI-assisted, or licensed), and time range. The /listen player shows the same chain alongside the player, and the active row pulses with the actual audio amplitude.

The /receipts directory

The /receipts page is the new front door for the system. Every documented chain on the platform, sorted by kind, with counts of elements / contributors / AI tools and a deep-link to the standalone receipt. Today it lists the 13 BHM tracks plus a growing number of producer-uploaded beats. As producers fill the upload wizard, their beats appear here automatically.

JSON-LD on every receipt

Every /receipt/<slug> page emits schema.org JSON-LD: a MusicRecording for tracks, a CreativeWork for beats, with creator, contributor, mentions (AI tools as SoftwareApplication entries), copyrightHolder, dateModified, and license fields. The /receipts directory emits two ItemLists — one for the static registry, one for producer-uploaded beats — so Google AI Overviews, Perplexity, ChatGPT, and Claude can ingest the full corpus as first-class data.

The producer rights wizard

Every beat uploaded through /upload can now ship with a documented chain from day one. The inline wizard captures contributors, AI tools, a structural preset that auto-generates element ranges from the audio duration, and a signed warranty. The data is sanitized server-side and persisted as JSONB. The /receipts directory, the BeatReceipt strip on /explore, the receipt page, and the JSON-LD all light up automatically. No extra step.

Copy or download the chain as JSON

On every documented receipt page there are two buttons under the warranty footer: Copy JSON and Download .json. The JSON-LD is for crawlers; this is for humans. Embed the chain in a contract. Attach it to a press kit. Feed it to a label compliance tool. The receipt now travels.

Why this matters

The 2026 conversation about AI music has stopped being about whether AI tools are allowed and started being about whether you can prove what they did. Disclosure is becoming a distribution requirement. Platforms are weighting provenance signals. The way most artists "document" their work — a paragraph in a press release, an EULA they never read — is structurally incapable of holding up to scrutiny.

A receipt that lives at a URL, renders as a page, exports as JSON, and indexes as structured data is a different category of artifact. It does not require lawyers. It does not require a label. It just has to ship by default. That is what we built.

What is now possible

• →When a buyer evaluates a beat in the marketplace, the receipt strip shows the chain inline. Click through for the full ledger. No registration required.
• →When someone searches Google or asks an AI assistant about a track or producer, the structured data on the receipt page is what the answer engines read. We become the answer.
• →When a producer uploads a beat, the wizard captures the chain at the source. The wedge scales without us babysitting each upload.
• →When a press release links a track, the receipt URL is what they paste. The receipt becomes the evidence.
• →When a label or distributor asks for provenance documentation, the answer is a one-click download.

What is next

A few things are queued: a WebGL variant of the stem visualizer for the cinematic upgrade, a producer onboarding email drip, a /methodology expansion with the full chain anatomy. But the core wedge is now operational. Every release that ships from this point forward ships with its receipt. That is the floor.

Try it: open /receipts to see the directory. Click any chain to see the receipt page. Hit "Download .json" to take the chain home. Or, if you produce beats: open /upload and watch the wizard.