Music labels — evidence and limits

Checked 5 October 2026. This is the evidence behind one residual placement question, not a complete entity, music-rights or pipeline audit. The meaning is now approved; no runtime change is claimed.

Prior decisions recovered

The original July A4 card recommends retaining company as the stored kind and describing a company's role separately. Joe approved it and emphasized company types such as brands, agencies, studios and production companies. Neither the original card nor his exact reply mentions Music Label. The current classification proposal explicitly proposes retiring its separate kind registration while keeping the company type.

The original sources are retained in the repository:

• docs/reference/2026-07/2026-07-21/ratification-console.html, original A4 card.
• docs/reference/2026-07/2026-07-21/theratificationcnooslejuly21.md, exact A4 reply and raw answer payload.
• Current classification proposal, entity classification section.
• Entities, the current conceptual model.

A bounded independent reviewer located the same limit; the root reviewer reread the original text. General approval is carried forward. The label-specific proposal was subsequently approved on 5 October; see the recorded answer. No stored-row count supplied that approval.

Selected live facts

The receipts entity-kinds-preflight.json and music-labels-preflight.json under docs/reference/2026-10/2026-10-04/ preserve exact read-only queries and results. The latter refreshes all six queries for this review. Schema inspection preceded the field-specific queries.

Surface checked	What it currently says
Physical entity_kind enum	Ten permitted enum values, including retired registry values
Active schema_enums entries for entity kind	Company, Person, Song, Artist and Music Label
Music Label company-type entry	Active; also allowed by the company-type check constraint
Grouped entity rows, including deleted rows	Company, Person, Song and Artist; no Music Label kind or company-type assignment
Local creation modal	Company, Person, Artist, Song and Music Label
Local backend creation allowlist	Company, Person, Event and Place

The selected table-constraint query returns no check narrowing the entity-kind enum. That does not establish what every trigger, permission policy or writer permits. The conformance script checks existing rows against four kinds; a successful row check does not demonstrate agreement among creation paths and registries.

The selected name predicate searched for Warner, Atlantic or Records and returned Fred Warner, The Atlantic and Virgin Atlantic. It did not return the inspected external labels. This predicate is not an exhaustive organization search, alias audit or entity-resolution test. Untyped companies must not be relabeled through name matching alone.

Local path and its limits

The creation modal calls useCreateEntity, which posts to the frontend admin entity route. That route requires the super-admin role and proxies the request to the backend entity route. The local backend rejects kinds outside its four-value allowlist before building the insert payload. The modal also offers Music Label among company types. These exact excerpts and source hashes are retained in the earlier receipt.

This establishes a local contract mismatch. It does not prove deployed-file equality or report an observed production creation failure. No create request, mutation or migration was run. All writers, identity resolution, relationship evidence, permissions, correction propagation, publication, search, saved trackers, scheduling and cost controls remain for the comprehensive trace.

The historical July external audit had already flagged disagreement among the kind definitions. It is a source lead, not current proof. This review relies on the fresh database reads and inspected local code above.

Inspected external example

Opened Warner Music Group's recording-artists page, which names Warner Records, Atlantic and Parlophone as labels. Its FAQ separately directs sound-recording and composition inquiries. These primary texts support the example and the warning against collapsing business relationships. They do not prove a particular recording's rights, complete ownership history or existing library membership. No media-analysis claim is made.

Architecture challenge

Retaining a separate kind gives labels a dedicated category but requires shared organization behavior and duplicate-identity handling across kinds. Removing all label classification would simplify the vocabulary at the cost of useful browsing. The selective recommendation keeps the company identity and the label classification while leaving specific relationship facts separately evidenced.

This does not approve one exclusive company role, a universal legal-entity model or a complete music ontology. A company that performs several roles exposes a separate multiplicity requirement. The implementation contract must cover all creation and update consumers, registry retirement, constraints, compatibility, corrections, migration or repair, verification and rollback. Physical changes remain outside this review.

Last reviewed 5 October 2026.