Distribution workflow
The AI disclosure gap starts before a track reaches the market.
Distributors, upload review teams, labels, catalog intake teams
By Art Clearance Certification · Updated
The upload moment is where origin ambiguity becomes expensive. A creator may submit a track with incomplete metadata, a vague AI disclosure or no structured evidence. The distributor then becomes the first operational filter between creator intent, platform policy and market risk.
Start with the metadata already in the workflow
DDEX's Recording Information Notification standard provides a way to capture recording-session metadata and communicate it along the music value chain. ACC should complement these established exchanges, not ask a distributor to discard them. Referencing RIN does not mean that ACC is DDEX-certified or that an automatic RIN integration is available.
The narrower job of an ACC record is to preserve a named declaration and its relationship to the exact submitted file. Keep delivery metadata, origin declarations and the distributor's acceptance policy as distinct inputs.
Upload teams inherit uncertainty
When an intake form asks whether AI was used, the answer can be too thin to be useful. A checkbox rarely captures the difference between AI-assisted mastering, AI-generated stems, human direction over generative output or fully synthetic music.
That creates a mismatch: platforms and partners increasingly need disclosure, while upload workflows often receive declarations that are not standardized, not hash-bound and not publicly verifiable.
Rejection loops are a weak user experience
If a platform rejects a track because disclosure is unclear, the creator experiences friction and the distributor absorbs support cost. If the track passes through without a clear origin signal, downstream systems inherit the ambiguity.
Neither outcome is efficient. The market needs a way to turn the creator declaration into a durable object before the track becomes another exception in someone else's queue.
ACC makes disclosure inspectable
ACC binds the declaration to a file hash and exposes a public verification page plus API object. A distributor can validate this without changing the whole upload stack: certify a reference track, verify the public page and read the API response.
The point is not to replace distributor policy. The point is to give policy a structured input: certified, not_certified, category, hash, status, identity level and evidence boundary.
ACC takeaway
The upload gap is where ACC can prove value quickly: fewer vague declarations, clearer review inputs and a status object partners can consume before distribution decisions become manual exceptions.
An intake checklist a distributor can test
- Ask who is making the declaration and capture the applicable acceptance version.
- Record the contribution of humans and generative tools before assigning a category.
- Bind the declaration to the final delivered file. Keep the original hash if a later encoding is created.
- Read certificate status, identity assurance and evidence limits independently. Do not reduce them to a single approved flag.
Compare incomplete submissions, repeat contact with creators and manual escalations. Treat improved completion as a pilot hypothesis, not a promised result.
Read the declaration categoriesSources and scope
External sources describe their own standards or observations. The proposed workflows are ACC's analysis, not an endorsement or partnership with the organisations cited.
Test this with your workflow
Bring one intake or catalog problem. Agree the evidence boundary and success measures before expanding the integration.
Request a partner pilot