DDEX ERN onboarding

DDEX ERN is a bilateral delivery program, not a public upload format. A valid XML document alone is insufficient to activate a sender or establish Kasty-specific rights.

Rights and identities

Kasty and the sender first establish the necessary implementation licence, DPID identities, delivery authority and rights responsibilities. Sender and recipient DPIDs identify exchange parties; they are not artist IDs or ownership proof.

Profile

Each sender freezes an agreed ERN version, Release Profile, mandatory fields, identifier rules, correction behavior, territories and supported resource types. The initial intended baseline is documented in the canonical DDEX mapping source and can change only through reviewed bilateral work.

Choreography

The agreement defines message sequence, transport, acknowledgements, resource transfer, retries, receipts and takedowns. An ERN message accepts durable work only after the selected choreography validates; it does not transcode audio inside a transport acknowledgement.

Mapping

The adapter preserves original ERN bytes and provenance, then maps the supported subset into kasty.music.delivery.v1. Unsupported constructs create stable review issues. The adapter never guesses video permission or silently drops rights data.

Conformance

Activation requires sender-specific fixtures, schema and profile validation, mapping review, idempotency tests, correction and takedown tests, asset transfer tests and a shadow-delivery comparison against expected canonical output.

Activation

Only Kasty can activate the sender after bilateral conformance. Until then DDEX is BILATERAL_ONBOARDING, and attempts fail before batch acceptance with a stable mapping or activation issue. Use Delivery channels for currently available alternatives.