Specification

v0.1-draft defines the canonical release model.

Labelcopy is organized as independently versioned specification families: JSON Schemas for music-industry entities and the LCX container format for exchange and archiving.

Schemas

Music entities with strict validation

The draft schema set covers release, edition, medium, group, track, party, work, recording, recording_version, resource, rights_profile, resolver, commit, tree, and manufacture_manifest. JSON properties use snake_case and JSON Schema Draft 2020-12.

LCX

Native release packages

LCX packages are intended to bundle metadata, works, recordings, editions, rights, and assets into a content-addressed release archive. The draft includes header structure, commit-rooted graphs, signatures, integrity validation, optional encryption, and future delta support.

Identity

Stable logical IDs and immutable content IDs

Logical IDs use the form lcid:type:ulid. Logical refs stay id-only, while content IDs bind exact immutable versions in trees, commits, resolver pointers, and other content-addressed fields. History is a hash-linked commit DAG; tree entries capture redirects and tombstones.

{
        "release_ref": {
          "id": "lcid:release:01HZY4YQJ3K9H8S4VR8B6GQJ3C"
        }
}