The Quiet Message in DistroKid's New AI Disclosure

When you upload a track to DistroKid now, there's a new question waiting for you.

"Does this song include AI-generated music, vocals, or lyrics? Using AI for mastering or mixing doesn't count."

That parenthetical at the end is doing more work than it looks like.

DistroKid is asking independent musicians to disclose AI use across three categories. Lyrics written by AI. Music composed by AI. Audio generated by AI. If you pick "all of the audio," they'll also ask whether your artist name represents a human or an AI persona. Spotify and Apple Music get the disclosure data and surface it to listeners.

On the surface, this is reasonable. AI is changing how music gets made. Listeners might want to know. Streaming services might want to track. Disclosure feels like the responsible move.

I'm not opposed to disclosure. I disclose everything I do. My books, my podcasts, my catalog — all of it is documented as Lane 2 work. Human-authored, AI-assisted. The methodology matters more than the label.

What I'm pushing on is the shape of this specific policy. Because the shape reveals something the industry hasn't said out loud.

The Exemption That Says Everything

Three things require disclosure: AI-generated audio, AI-generated lyrics, AI-generated compositions.

Three things are exempt: pitch correction and auto-tune, AI-assisted mixing or mastering, AI-assisted workflows.

Read those two lists next to each other.

The required disclosures all target the creative front of the production process. The artist's voice. The songwriter's words. The composer's melody. The performer's audio. These are the spaces where artists make their work, and the industry now requires those artists to label any AI involvement.

The exempt categories all target the production back-end. Mixing. Mastering. Workflow tools. These are the spaces where engineers and producers do their work. The industry has decided AI involvement in those spaces doesn't warrant disclosure to listeners.

The industry just told the entire mixing and mastering profession that AI doing their work doesn't matter enough to mention.

Listeners don't need to know if your master was created by a human or an algorithm. The craft is invisible. The role is exempt. The implication is that mixing and mastering have already crossed into commodity territory where the human is replaceable enough that disclosure would be a formality.

If you're a mixing or mastering engineer reading this, your industry just confirmed in policy form what you've probably been suspecting in practice.

The Loophole Inside the Loophole

"AI-assisted workflows" is the third exempt category, and it's the one nobody is talking about.

What's an AI-assisted workflow versus AI-generated content? The policy doesn't say.

If a major label studio uses an AI tool to generate stem ideas, then re-records them with session musicians, is that an AI-assisted workflow or AI-generated music?

If a producer uses an AI tool to suggest chord progressions that get refined by humans, is that AI-assisted or AI-generated?

If a vocal track gets processed through AI-driven processing chains that fundamentally reshape the performance, is that mixing or generation?

The lines are not drawn. They're left to interpretation.

That ambiguity benefits one category of music maker much more than another. A major label studio with attorneys can plausibly argue most of their production falls under "AI-assisted workflows" and exempt themselves from disclosure entirely. An independent musician who used Suno to generate a vocal track cannot make that same argument.

Same policy. Very different outcomes.

The Honesty Penalty

The structure of this disclosure creates a problem the policy doesn't address.

If most artists choose not to disclose, and a few do, the disclosing artists become the visibly-AI tracks in the streaming feed. The actual AI tracks released without disclosure float by unmarked.

Honesty becomes a competitive disadvantage. The artists who follow the rules wear a label. The artists who don't follow the rules look like everyone else.

The policy creates an incentive structure that punishes the behavior it claims to reward.

This is fixable. Apply the policy universally and enforce it consistently. But the policy doesn't say how enforcement works. It doesn't say how AI use gets verified. It doesn't say what the consequences are for non-disclosure. The whole apparatus rests on the honor system, and the honor system collapses the moment someone realizes there's no penalty for staying quiet.

What Happens With the Data

The policy doesn't explain what streaming services will do with the AI flag.

Will Spotify deprioritize flagged tracks in algorithmic recommendations? Will Apple Music exclude them from editorial playlists? Will royalty rates be adjusted? Will certain features be fenced off from disclosed content?

None of this is stated. The policy asks for transparency without offering reciprocal transparency about what the data enables.

"Give us this information about your work" without explaining "and here's what we'll do with it" is not transparency. It's data collection dressed as principle.

If the disclosure has no consequences, why ask for it at all? If the disclosure does have consequences, those consequences should be stated in advance so artists can decide whether the trade-off is acceptable.

The Asymmetric Application

Independent musicians release through DistroKid. Major labels don't.

This policy applies to you. It does not apply to the artists at major labels using AI in ways they don't disclose.

The artists most likely to be using AI heavily are the ones least likely to be subject to mandatory disclosure. The artists with the smallest legal teams are the ones being asked to label their work. The artists with the largest production budgets get to invoke "AI-assisted workflows" as a catch-all that exempts them from the same scrutiny.

This is asymmetric enforcement, and asymmetric enforcement is asymmetric harm. The transparency burden is being placed on the people with the least power to push back.

The Grey Area Problem

Where exactly is the line?

If you wrote lyrics yourself but Suno generated the melody, is that AI?

If you generated stems in Suno and re-recorded the bass live in your DAW, is that AI?

If you used an AI co-writing tool that suggested chord progressions, then chose which ones to develop, is that AI?

If you used Suno to generate reference material, then built the track from scratch in Reaper, is that AI?

The policy treats AI use as binary. Yes or no. Disclose or don't. The reality is a spectrum. Most thoughtful artists working with AI tools fall somewhere in the middle, and the policy doesn't have a category for them.

Lane 2 work — human-authored, AI-assisted music creation — sits squarely in that middle. The artist has authored the work. The AI has assisted. Where does that go in DistroKid's disclosure form?

The honest answer for most Lane 2 work is "Part of the audio." That's the category I'll be using going forward. But the policy doesn't really know what to do with that answer either, because the rest of the form assumes you're either disclosing extensively or not at all.

The Retroactive Question

What about catalogs released before this disclosure existed?

The policy doesn't say. There's no mention of grandfathering, no mention of retroactive flagging, no mention of historical catalogs.

If transparency matters, why does it only matter starting now?

If catalogs released last year contained AI-generated music without disclosure, and those tracks continue earning royalties on streaming platforms, the policy is admitting that disclosure isn't really about transparency. It's about creating a forward-looking checkbox that demonstrates good faith without imposing actual cost.

If artists are expected to retroactively flag past catalogs, the policy hasn't told them. There's no email asking them to update old releases. There's no enforcement mechanism. The catalogs sit unmarked.

Either answer reveals the policy is incomplete.

What Real Transparency Would Look Like

I'm not arguing against disclosure. I'm arguing this isn't disclosure. This is window dressing that looks like disclosure.

Real transparency would apply universally. Major labels and independent artists. Performance and production. Every link in the chain that touches AI.

Real transparency would define the terms precisely. What counts as AI-generated. What counts as AI-assisted. Where the line is. The policy would not leave the answer to interpretation by whoever has the bigger legal team.

Real transparency would explain what happens with the data. What streaming services do with the flag. How it affects royalties, recommendations, playlist consideration. The trade-off would be stated in advance.

Real transparency would address mixing and mastering with the same scrutiny applied to performance. If AI is changing music production, the production back-end is part of music production. Pretending otherwise is the industry telling engineers their work doesn't count.

Real transparency would handle the retroactive question. Either grandfather old catalogs explicitly and explain why, or require updates and explain how.

The policy DistroKid rolled out does none of this. It asks independent musicians to label their AI use without applying the same standard universally, without defining the terms, without explaining the consequences, and without addressing the obvious gaps.

This is PR, not policy.

What I'm Doing

I disclose everything. That doesn't change because the disclosure system is incomplete.

Lane 2 work is what JG BeatsLab is built on. Human-authored, AI-assisted music creation. The methodology is documented, the process is open, the catalog reflects the work. I will continue to disclose AI use on every release because the disclosure is consistent with how I operate, not because a checkbox required it.

But I'm not going to pretend this policy is what it claims to be.

If the music industry wants real transparency about AI, the industry should build a real transparency policy. Apply it universally. Define the terms. Address every part of the production chain. Explain the consequences.

Until then, what we have is a checkbox for independent musicians and a loophole for everyone else.

The mixing and mastering engineers have already gotten their message. The rest of us are still waiting for the policy that takes its own premise seriously.

— Josh Founder, JG BeatsLab