7-lesson course · about 15 hours

Run supervised agent teams around one shared release record

For Artists, producers, managers and music teams responsible for creative decisions, release preparation and the details that connect them

Everything for Music teams

Coordinate Creative Assets, Release Operations and Campaign teams in Dots or Claude Duet. Handle late changes and restarts, and leave every release decision with the artist.

Try lesson 1 freeSee what you’ll learn

What you’ll be able to do

By the end, you can…

Give each team its own laneSet up three agent teams: Creative Assets, Release Operations and Campaign. Each one gets at least two named roles, its own job and a named recipient for its work. All three work from one shared release record that shows who wrote, who played, who consented to what and who called the take.
Put a check on every handoffBuild a handoff table that lists the sender, the receiver, what passes between them, the acceptance check, who accepts it and what happens if it fails. Write checks for the audio version manifest, the credits and rights review (CSV) and the campaign sequence (ICS). No team approves its own release decision, and Campaign writes only from facts the other two teams have accepted.
Run the Factory in Dots or Claude DuetConnect your chosen agent only to the files and apps the sample packet needs. Write instructions that tell it to follow the approved record. Then run the packet through the handoffs with the waiting periods shortened. Each run returns a current release record, the drafts the change affected and the artist or rights decisions that are still open.
Handle a late change without damageA revised master and a release date moved by a week arrive in the same hour. Every team stops. The replaced master stays on record, and any draft carrying the old date is pulled. No team starts again until all three share the same facts.
Test, tighten and judge for reuseTest the Factory with duplicate files, changed files, conflicting credits, blocked work and a run cut off partway through. Trace each failure back to a missing boundary, retry limit or escalation owner, and fix the instructions. Then run a second batch and judge whether the process can be used for your next release.
Record the release decisionThe artist and the release owner mark every open item approved, returned or stopped, with a reason and an owner. They name the one person allowed to deliver. The result is a record another operator can read without asking anyone.

How it works

A tutor that meets you where you are

  1. Lessons pitched to your levelThe seven lessons adjust to what you already know. If you have run agents for release work before, you move quickly to building the teams. If a step is new to you, the lesson slows down and explains it.
  2. An AI tutor you can ask anythingAsk questions by typing or out loud while you work. For example: how to word an acceptance check, whether a stop was the right call, or how to pass a moved date through Campaign. The tutor works from your own sample packet and handoff table.
  3. Quizzes and flashcards for each lessonShort quizzes and flashcards are tied to each lesson. They cover the rules that matter under pressure: stop all and resume together, a later file doesn't win just because it arrived later, and the team that prepares the work never approves it.
  4. Progress tracking and a certificateTrack your progress through the three modules and pick up where you left off. When you finish, you get a certificate of completion.

Curriculum

The curriculum

The course has seven lessons in three modules, following the release from planning through to the decision. First you give the teams a shared operating plan. Next you keep them in step when the plan changes. Finally you test the system and approve it for another release.

Module 1Give release proactive AI agent teams a shared operating plan.2 lessons

  1. 1Assign the release proactive AI agent teams
    • Explain why a release needs lanes and guardrails once more than one agent is working on it, using Jimmy Jam's roads analogy.
    • Assign Creative Assets, Release Operations and Campaign, each with at least two named roles, a distinct lane and a named downstream recipient.
    • Build the first version of a shared release record that shows who wrote, who played, who consented to what and who called the take.
    • Choose a scoped sample release packet that needs creative assets, release information and campaign work to agree.
  2. 2Set the acceptance checks
    • Build a handoff table that lists, for each handoff: sender, receiver, what passes, the acceptance check, who accepts it, and what happens when it fails.
    • Write acceptance checks for the audio version manifest (STEMS), the credits and rights review (CSV) and the campaign sequence (ICS).
    • Explain how the checks stop a disputed credit, a new date or a generated sketch from becoming an approved fact.
    • Name an escalation owner for every check that can fail.

Module 2Keep the proactive AI agent teams in step when plans change.2 lessons

  1. 3Pass the release between proactive AI agent teams
    • Choose Dots or Claude Duet and connect it only to the files and apps the sample packet needs.
    • Write run instructions that tell the agent teams to follow the approved record and return a current release record, the affected drafts and the outstanding artist or rights decisions.
    • Run a scoped release packet through the handoff table with waiting periods compressed.
    • Review the returned record against your handoff table and spot any handoff that skipped its acceptance check.
  2. 4Resolve a late change
    • Explain the 'stop all, resume together' rule and the spread line.
    • Build the late-change instructions for each team: what it stops, what it keeps, what it pulls and what it rebuilds.
    • Test the change in Dots or Claude Duet and confirm that no team resumes before all three share the same facts.
    • Choose which open items go to the artist and the release owner, and which a team can handle on its own.

Module 3Approve the system for another release.3 lessons

  1. 5Tighten proactive AI agent team instructions
    • Test the Factory against duplicate inputs, changed inputs, conflicting credits, blocked work and a run interrupted partway through.
    • Explain each failure you find in terms of a missing boundary, retry limit or escalation owner.
    • Build revised team instructions with clear boundaries, retry and reminder limits, and a named escalation owner for each kind of stop.
  2. 6Run a second sample batch
    • Run a second sample batch through all three teams with the revised instructions and compressed timing.
    • Compare the second run's release record, affected drafts and open decisions with the first run's.
    • Judge whether the process can be reused by checking it against clear criteria, and record what still needs work.
  3. 7Record the release decision
    • Explain why the final release decision belongs to the artist and the release owner and not to any agent team.
    • Build a decision record where every open item is marked approved, returned or stopped, with a reason and an owner.
    • Name the one person allowed to deliver, and record what must happen before they do.
    • Test the record by checking that another operator could see what's approved, what's blocked and what's still needed before delivery.

Who it’s for

Made for you if…

Made for: Artists, producers, managers and music teams responsible for creative decisions, release preparation and the details that connect them

Independent artists and producers who run their own releases

You already use single agents for intake, credits or campaign drafts. Now the trouble is in the handoffs: the wrong bounce gets uploaded, or an old date survives in a pre-save link. This course gives those handoffs checks and a single record.

Artist managers

You stand between the artist's decisions and the release work. You need a system that brings disputed splits and missing files to the right owner and never decides on the artist's behalf.

Small label or release teams of two or three people

You want a release-support process that holds up through a late change and that another operator can pick up and read.

Questions

Good to know

What do I need to know before starting?

You should have finished days 1–7 of the Music track or have the same experience. That means you can write a release brief, build a track sheet that keeps composition and recording credits separate, and write copy only from approved facts. You should also have run single proactive agents for release chores in Dots or Claude Duet, and know how credits, splits, version names, pre-save links and distributor specs work.

Do I need Dots or Claude Duet?

Yes, you need access to one of them, connected to the files and apps you use for release work. The course treats them as equals. You choose one in lesson 3.

What material do I practise on?

A small sample release packet you have permission to use: masters or versions, artwork, a credits and splits sheet, a campaign draft and a distributor spec. You can use your own material or the course's sample.

Will the agents submit my release or publish posts?

No. The Factory prepares the release, and people deliver it. The course does not cover submitting to a distributor or publishing campaign posts, and you won't finish or distribute a real release during it. The goal is a reusable release-support system.

Does the course give legal advice on contracts, samples or voice rights?

No. The course teaches you to flag these questions for the artist, the release owner and the rights holders. It does not give legal advice on contracts, sample clearance, voice licensing or ownership disputes.

Does it cover mixing, mastering or marketing strategy?

No. Mixing and mastering technique, judging sound on the artist's behalf, marketing strategy, ad spend and playlist pitching are all outside this course. Only a person accepts the musical result.

How long does it take?

About 15 hours, at your own pace.

Music AI Capstone: supervised agent teams around one release record

$397

One payment · lifetime access

  • 7 self-paced lessons in 3 modules, adjusted to your level
  • Build a handoff table with acceptance checks for the audio manifest, the credits and rights CSV and the campaign ICS
  • Hands-on runs in Dots or Claude Duet on a sample release packet, including a late change and a restart
  • An AI tutor you can ask anything, typed or out loud
  • Quizzes and flashcards for each lesson, plus progress tracking
  • Certificate of completion

Secure checkout by Stripe. Have a promotion code? Enter it at checkout.

Refunds: Full refund if you ask before you open your first lesson. Once you’ve started, purchases aren’t refundable, except where the law gives you that right.

Already bought it? Sign in