AI Music Revolution

The Disclosure Discipline for AI Assisted Music

• Josh • Episode 25

Share episode

Use Left/Right to seek, Home/End to jump to start or end. Hold shift to jump forward or backward.

0:00 | 18:03

Send us Fan Mail

DistroKid quietly added a mandatory AI disclosure question to every upload. Three categories require disclosure: AI-generated lyrics, AI-generated music, AI-generated audio. Three categories are exempt: pitch correction and auto-tune, AI mixing and mastering, and AI-assisted workflows. The structure of the exemptions reveals something the music industry hasn't said out loud about how it views mixing engineers, mastering engineers, and the major label production paths most likely to be using AI heavily right now.

The "AI-assisted workflows" exemption is undefined. A major label studio with attorneys can plausibly argue most of their production falls under that exemption. An independent musician who used Suno to generate a vocal track cannot make the same argument. Same policy, very different outcomes. The artists most likely to be using AI heavily are the ones least likely to be subject to mandatory disclosure. The transparency burden is being placed on the people with the least power to push back.

That's the policy landscape. The operational response is what most creators get wrong.

Most independent AI music creators have settled into one of two postures. The first is hiding. Upload tracks without disclosure, hope the detection systems miss it. That worked in 2023. It does not work in 2026. Spotify's DDEX AI credit infrastructure went live in April. Deezer has flagged over 13 million tracks via its own AI detection system and excluded them from editorial and algorithmic playlists. SubmitHub rolled out internal detection. The probability of being identified is now higher than the probability of slipping through, and identification costs the catalog real ground.

The second posture is apologizing. Disclose reluctantly, with framing that signals embarrassment about the production method. The reader infers exactly what the writer is telegraphing: that the work is lesser, that the artist agrees with the people who hate AI music. The apology becomes the frame, and the work has to climb back out from underneath it.

The third option, which almost nobody is taking, is the Disclosure Discipline.

The episode walks through the four operational components. Disclose accurately in distributor metadata using DistroKid's DDEX-aligned AI credit fields. Lead with the workflow plainly in SubmitHub pitches and curator outreach. Describe the production method matter-of-factly in the artist bio. Document the human authorship rigorously for sync submissions where most major libraries will not accept undisclosed AI involvement.

The strategic argument behind all four components: the 45 to 65+ audience the Unlock System is built for has spent decades inside creative fields. They know tools have always been part of the work. The objection to AI is rarely about tools as a category. It's about deception, displacement, and craft erosion. A Lane 2 creator who discloses cleanly is operating against all three concerns at once. Disclosure done well moves the creator from defendant to operator. The frame changes.

This episode is the spoken companion to two pieces from the JG BeatsLab blog: the May 18 Monday Manifesto on the DistroKid AI disclosure policy, and the May 22 Friday Informative Bits on why hiding and apologizing are both losing positions in 2026.

If you want the complete Disclosure Discipline framework, including the platform-by-platform enforcement landscape, the EU AI Act timeline, the sync supervisor segmentation, and the distributor comparison for AI-assisted creators, Unlock Music Promotion is the book. Chapter 3 covers all of it. Available for $9.99 on the JG BeatsLab site and on Amazon. Or grab it bundled with Unlock Suno: The Complete Guide and Unlock Music Rights and Registration in the Minimum Starter Kit at jgbeatslab.com/store for $27. Everything Josh publishes lives inside Red Lab Access for $117 lifetime at jgbeatslab.com.

Subscribe so you don't miss next Friday's episode. Find more at jgbeatslab.com.


The Unlock System is JG BeatsLab's methodology for serious musicians working with AI tools. Lane 2 work: human-authored, AI-assisted music creation.

Visit JG BeatsLab: https://www.jgbeatslab.com

The JG BeatsLab Newsletter. One email a week, Thursdays. Studio work, Red Lab research, and methodology in real time. Free signup on the homepage at jgbeatslab.com.

Subscribe to the Newsletter: https://www.jgbeatslab.com/newsletter

Red Lab Conversations is produced by JG BeatsLab LLC, an AI music education company building the methodology, research, and community for serious creators working in Lane 2.

Get more from JG BeatsLab LLC:

Connect:

Contact: josh@jgbeatslab.com

Stop gambling. Start directing.

SPEAKER_00

Hello and welcome to the AI Music Revolution. I am your host, Josh Kittle Man, the founder of JG Pizza. Today's episode, by the way, which is episode 25, believe it or not, uh it's about a question DistroKid added to every upload a few weeks ago. The message buried inside that question that the music industry has been wanting to send for a long time, and what an independent AI music creator actually does about this. Because there are two postures most creators have settled into right now, and both of them lose. Hiding loses. Apologizing loses. There's a third option, and almost nobody is taking it. And that's what we're going to walk through. We're going to look at the policy first, the shape of the distrokid disclosure form, and what the exemptions tell you about how the industry sees independent musicians, mixing engineers, and the major label production paths most likely to be using AI heavily right now. Then we're going to land on the operational response. Four specific components of what I call the disclosure discipline, which is what a lane two creator does instead of hiding or apologizing. This is the AI music revolution. Let's get into it. Here's the question DistroKid is now asking on every upload. Does this song include AI generated music, vocals, or lyrics? Using AI for mastering or mixing doesn't count. Three sentences. Looks reasonable. AI is changing how music gets made. Listeners might want to know. Disclosure feels like the responsible move. I'm not opposed to disclosure. I disclose everything I do. The methodology matters more than the label, but I want to push on the shape of this specific policy because the shape reveals something the industry hasn't said out loud. Three categories require disclosure AI generated audio, AI generated lyrics, AI generated compositions. Three categories are exempt pitch correction and auto tune, AI assisted mixing or mastering, AI assisted workflows. Read those two lists side by side. 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 in those spaces. The exempt categories all target the production backend, mixing, mastering, workflow tools. These are the spaces where engineers and producers do their work. The industry has decided AI involvement in those spaces does not warrant disclosure to listeners. Let that land for a second. The industry just told the entire mixing and mastering profession that AI doing their work doesn't matter enough to mention. 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've been hearing for years that AI mastering tools are almost as good as the real thing, this is the industry confirming in policy form that they agree. That's the first thing the policy says out loud without saying it out loud. The second thing is harder to see, but it's the part that affects you more. The third exempt category is AI-assisted workflows. That's the one nobody is talking about. What is an AI-assisted workflow versus AI generated content? The policy doesn't say. The line is not drawn, it's left to interpretation, and that ambiguity benefits one group more than another. 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? A producer uses an AI tool to suggest chord progressions. Then the songwriting team refines and develops them. Is that AI-assisted or AI generated? A vocal track gets processed through AI-driven processing chains that fundamentally reshape the performance. Is that mixing or is that generation? The policy doesn't answer any of those questions. 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 uses Suno to generate a vocal track cannot make that argument. They don't have a legal team to define their way out of disclosure. They just have a checkbox. Same policy, very different outcomes. And here's the structural piece. Independent musicians release through DistroKit. Major labels don't. So this policy applies to you. It does not apply to the artists at major labels who are using AI in ways that they're not going to disclose. The artists most likely to be using AI heavily in production are the ones least likely to be subject to mandatory disclosures. 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. An asymmetric enforcement is asymmetric harm. The transparency burden is being placed on the people with the least power to push back. Okay, that's the policy. That's the landscape you operate in. Now, what do you actually do about it? Most independent AI music creators have settled into one of two postures, and both of them lose in 2026. The reason both lose is structural, it's not philosophical. The first posture is hiding. Upload tracks without disclosing. Hope detection misses. Hope nobody asks. That worked in 2023. It doesn't work now. Spotify's AI credit infrastructure went live in April. Deezer has been running its own AI detection system against its catalog and has flagged over 13 million tracks as AI generated, all of which are excluded from editorial and algorithm playlists. Submit Hub rolled out an internal AI detection tool. Watermarking and provenance standards are moving into the AI content ecosystem. Detection tools are improving across platforms. The probability that a curator, a platform, or a competitor identifies undisclosed AI in your catalog is now meaningfully higher than the probability that you slip through. And when the identification happens, it does not arrive as a quiet note. It arrives as a curator decline, a playlist removal, a flag against your distributor account, hiding loss the moment detection became the systematic, and detection became systematic this year. The second posture is apologizing. Disclose reluctantly with framing that signals embarrassment without a production methodology. The verbal equivalent of I use some AI tools, but I really did most of it myself, I promise. This loses for a different reason. The reader of an apologetic disclosure infers exactly what the writer is telegraphing. The work is somehow lesser. That the production process is shameful, that the artist is on probation. That framing follows the work everywhere you go. Listeners do not respond to apologetic positioning by extending sympathy. They respond by deciding the artist agrees with the people who hate AI music. The apology becomes the frame. The work has to climb back out from underneath it. Most work cannot. So hiding loses to detection. Apologizing loses to framing. The winning posture is the third option, and almost nobody is talking about it. The disclosure discipline is what the lane to creator does instead. It has four operational components, and I'm going to walk through each one because they each cover a different platform context. The first component is the distributor metadata. Disclose accurately at upload. DistroKid supports DDX aligned AI credit fields. Use them. The field should name the AI tools involved, identify the human creative rules, and describe the workflow in a matter-of-fact language. Something like vocals generated using Suno, lyrics written by Josh Gilliland, arrangement mixing and mashing by Josh Gilliland. This documentation is for platforms and supervisors, not for listeners. It travels invisibly behind your release and creates the compliance record that protects you when policy enforcement tightens. Disclosed compliance ages better than undisclosed avoidance every time. The second component is submit hub pitches and curator outreach. Lead with the workflow plainly in a personalized message field. This track was created using AI tools for vocal synthesis with human production, mixing, and final curation. I think it fits the mood of your playlist. A curator who is categorically anti-AI declines the pitch. That's a small loss because the same curator would have declined and damaged the relationship if they discovered the AI involvement after acceptance. A curator who is AI neutral or AI positive reads the pitch, evaluates the work on its merits, and respects the transparency. The net trade is favorable every time. The third component is the artist's bio across platforms. Describe the production method in the same register you would describe any other creative process. AI assisted production with human arrangement and final mixing. Not a confession, not a defense, a description. The listener who cares about the work reads it and understands the workflow. The listener who is hostile to AI has already decided based on the sound, not the bio. The bio is not the place to fight the battle. It's the place to set the record straight in three or four words and move on. The fourth component is sync submissions and licensing pitches. This is the one where disclosure becomes not negotiable. Most major sync libraries will not accept undisclosed AI involvement. The liability for the supervisor is too high. Include a one-line production note in the submission. AI assisted with human arrangement and mixing. Have your DAL project file ready as proof of human authorship if challenged. Sync supervisors who are AI friendly will work with you. Sync supervisors who are AI hostile will pass. The middle category, supervisors who are AI cautious, will accept transparency and reject deception. That's the segment that grows the most when you disclose. Four components distributor metadata, curator outreach, artist bio, sync submissions. Each one is a different platform context with a different audience and a different penalty for getting it wrong. The discipline is operating all four consistently across the catalog. I want to land on why this works, because I think the strategic point is more important than the tactical one. The 45 to 65 plus audience the unlock system is built for has spent decades inside creative fields. They know tools have always been a part of the work. A guitarist with an effects pedal is using a tool. A matching engineer with a compressor plugin is using a tool. A photographer with Photoshop is using the tool. The objection to AI is rarely about the tools as a category. It's about deception. Displacement, craft erosion. A lane two creator who discloses cleanly is operating against all three of those concerns at once. The deception complaint does not apply, because you disclosed. The craft erosion complaint loses force when the human creative direction is visible. The displacement complaint shifts from AI is replacing musicians to this musician is using AI deliberately and openly, which is a different conversation entirely. Disclosure done well moves the creator from defendant to operator. The frame changes. You're not asking for permission, you're not apologizing for the workflow, you're describing how the work got made and letting the work stand on what it is. The listener who reads AI assisted with human arrangement and mixing, and then hears work that holds up, will reach the conclusion that the work earns. The listener who is hostile to AI was never the customer. The listener in the middle, the one who doesn't care about the production method, as long as the music works, gets the music and ignores the metadata. Three audiences, one disclosure, no contradiction. That's the positioning advantage. Disclosure is not a tax on lane two work. It's the move that makes lane two work credible at scale. The full disclosure discipline framework, including the platform-by-platform enforcement landscape, the EU AI Act Timeline, the Sync Supervisor Segmentation, and the Distributor Comparison for AI assisted creators, lives in chapter 3 of Unlock Music Promotion, 999 at JGBeatslab.com or on Amazon. If you want it bundled with Unlock Suno, the complete guide, and Unlock Music Rights and Registration, those three together are the minimum starter kit at jgbeatslab.com backslash store for $27. Make it, release it, promote it. The full production, registration, and promotion triangle for a disclosed link to release. And if you want everything I publish, every book, every research report, every blueprint, the sprint course, fader, and the community of people doing this work with intention, Red Lab Access is the move. One price, lifetime access, $117 at JGBslab.com. The form is incomplete. The policy is asymmetric. The detection is real. None of that changes what you do. Disclose accurately. Lead with the workflow. Document the creative roles. Let the work stand on what it is. The disclosure discipline is not a defense. It's an operating posture. And it ages better than every alternative. Stop gambling. Start directing. Thanks for listening. New episodes every Friday. Subscribe so you don't miss next week. I'll see you then.