10 live days · Your work, in practice
Direct a Factory for release preparation.
Choose MasterCourse for all ten days, including the Capstone that connects creative assets, release information and campaign preparation across proactive AI agent teams.
A release depends on more than a finished track. Learn to turn artist notes into useful prompts, keep versions and credits moving through supervised proactive agents, and direct a Factory of proactive AI agent teams that prepares a release for your decision.
Keep the artist’s intent intact while coordinating audio versions, contributor information, approved messaging and delivery requirements. Missing information should reach its owner before it becomes a release problem.
What you learn
Learn to connect music prompts and release proactive agents into a Factory of supervised proactive AI agent teams, with clear handoffs and artist approval before delivery.
Build a Factory of proactive AI agent teams for release preparation. Use a Dot to coordinate continuing work across their handoffs and return a current release record, affected drafts and outstanding artist or rights decisions. Test changing inputs, blocked work and a later restart. The artist and release owner approve creative decisions, rights and distribution.
Proactive Agents · OpenAI Dots
Create it. Name it. Put it to work.
Create and test a proactive AI agent, give its role a stable name, and define what it may do. Then hand supported work to OpenAI Dots for one run or a continuing responsibility. Your Dot can keep working between conversations, using approved context and connected tools, and return results or ask for a decision without a fresh prompt for every step.
Give the role a name and a brief
Name the role Release Desk. Give it the release identifier, approved assets, credits, listening decisions and delivery requirements. Connect only the permitted release folder or provide reviewed previews; preserve accepted versions and artist decisions across runs.
Choose a run or an ongoing responsibility
A Dot has its own cloud computer and browser. When the assignment, files and tools are available there, it can work while your phone or computer is off. Always-on means available to continue the responsibility; it may wait for a schedule, input or approval and remains subject to access and usage limits. Work using local files or applications still needs that connected computer online with the ChatGPT app open.
Set the return and the review rhythm
Return a current release record, affected drafts and outstanding artist or rights decisions under the same named responsibility, with source versions and completed, waiting and blocked work clearly separated. Agree whether you need a scheduled report, an update on a material change, or a decision request. The artist and release owner approve creative decisions, rights and distribution.
Agree when results are due, which changes deserve an alert and where to review them. Confirm recurring schedules, time zones and end dates; connecting an app alone does not enable monitoring. Test a changed input and a blocked step. Before retiring the responsibility, stop its delegated work and cancel its schedules separately. Keep the reviewed instructions so you can recheck access and resume when needed.
Connect only what the role needs
Use cleared sample audio and approved release information. Protect unreleased masters, private contracts and contributor details. A Dot does not establish ownership, clear samples or authorize voice imitation; the rights holder and release owner control those decisions and distribution.
Cloud preparation can use approved release records and accessible preview files. A local audio workstation or private master library still needs its own authorized access and an available computer.
This practice is part of the existing proactive agent assignments and review time. It does not add class days or extend the hours shown in your booking.
The learning map
Work units by day
10 days of practical work for Artists, producers, managers and music teams responsible for creative decisions, release preparation and the details that connect them. Every unit below has an output and a review point.
Your learning plan: these are the tasks you will practice. The time suggested for each task is a guide; your booking shows the confirmed class dates and start and end times.
Artist intent · Listening references
Turn artist notes into a working brief.
- 1.1Write the artist brief
- 1.2Compare musical directions
- 1.3Record the listening decision
Credits · Release information
Prepare a track for a clear review.
- 2.1Draft the track-information sheet
- 2.2Write release copy
- 2.3List release questions
Release intake · Version control
Keep new assets tied to the release.
- 3.1Register incoming assets
- 3.2Handle repeats and missing files
Contributor records · Metadata
Keep credits and metadata consistent.
- 4.1Compare contributor records
- 4.2Escalate conflicting credits
Audio versions · Listening review
Turn listening notes into the next revision.
- 5.1Prepare the listening queue
- 5.2Track feedback to resolution
Release messaging · Campaign preparation
Keep campaign drafts aligned with the release.
- 6.1Prepare a dated content queue
- 6.2Rebuild only affected drafts
Delivery requirements · Exceptions
Assemble a release package for approval.
- 7.1Check the delivery manifest
- 7.2Test a delayed approval
Factory · proactive AI agent teams and shared records
Give release proactive AI agent teams a shared operating plan.
- 8.1Assign the release proactive AI agent teams
- 8.2Set the acceptance checks
Factory · Change and coordination
Keep the proactive AI agent teams in step when plans change.
- 9.1Pass the release between proactive AI agent teams
- 9.2Resolve a late change
Factory · Approval and repeat use
Approve the system for another release.
- 10.1Tighten proactive AI agent team instructions
- 10.2Run a second sample batch
- 10.3Record the release decision
The work behind the map
Daily detail
Follow the work from its starting material to a result you can inspect. Each checkpoint gives you a reason to approve, revise or stop.
Intro
Days 1–2 · Tasks
Frame a useful first pass.
Direct one important task at a time. Give the prompt enough context, inspect the result and improve it before reuse.
Day 01Turn artist notes into a working brief.
Start with one short musical idea and a supplied set of notes. Use prompts to make the creative direction explicit, then compare a small set of sketches without handing over the listening decision.
- 1.1
Write the artist brief
Turn the supplied artist notes and listening references into a brief covering mood, audience, arrangement and constraints. Mark assumptions for the artist to confirm.
Suggested time for this task: 1 hour in Full Course; 30 minutes in Crash Course. Part of your class day, not extra time.- Practice result
- A one-page artist brief with open questions.
- 1.2
Compare musical directions
Use the approved brief to prepare Suno prompts for a few contrasting sketches. Keep the prompt and version alongside each permitted export.
Suggested time for this task: 1 hour 20 minutes in Full Course; 40 minutes in Crash Course. Part of your class day, not extra time.- Practice result
- A small sketch comparison with prompts and version labels.
- 1.3
Record the listening decision
Listen to the sketches against the brief. Prompt a concise comparison from your notes, separating audible observations from creative preferences.
Suggested time for this task: 1 hour 40 minutes in Full Course; 50 minutes in Crash Course. Part of your class day, not extra time.- Practice result
- A listening memo explaining the selected direction and revisions.
By the end of the day
A reusable creative prompt set and a listening brief for one scoped musical idea.
Review checkpoint
Check that the memo reflects what you heard and the artist’s intent. A generated sketch does not establish permission to release it.
Day 02Prepare a track for a clear review.
Move from the musical idea to the information surrounding it. Practice separate prompted tasks on a supplied track packet before connecting them into recurring work.
- 2.1
Draft the track-information sheet
Use the supplied contributor notes to draft titles, version names and contributor fields. Keep composition and recording information distinct; leave unsupported fields unresolved.
Suggested time for this task: 1 hour in Full Course; 30 minutes in Crash Course. Part of your class day, not extra time.- Practice result
- A source-linked track-information sheet.
- 2.2
Write release copy
Draft a short release description and two audience-specific announcements from approved artist facts. Remove invented achievements and claims.
Suggested time for this task: 1 hour 20 minutes in Full Course; 40 minutes in Crash Course. Part of your class day, not extra time.- Practice result
- A reviewed release-copy set.
- 2.3
List release questions
Compare the audio and asset list with supplied delivery requirements. Identify missing credits, permissions questions and decisions needing an owner.
Suggested time for this task: 1 hour 40 minutes in Full Course; 50 minutes in Crash Course. Part of your class day, not extra time.- Practice result
- A release checklist with owners and unresolved items.
By the end of the day
A checked information sheet, approved-copy draft and release-question list.
Review checkpoint
Trace names and credits to the supplied records. Keep permissions and eligibility decisions with the relevant people.
Intensive
Days 3–7 · Proactive Agents
Keep recurring work moving.
Build proactive agents that run defined tasks over time. Give each one a trigger, working record and limits, then review its exceptions and results.
Build the proactive agent and test one complete run. Name its role, approve its inputs and connections, then hand suitable work to a Dot. Choose a single assignment or a continuing responsibility with clear reports, review points and a way to stop.
Day 03Keep new assets tied to the release.
Build a proactive intake agent that runs when an approved folder or submitted manifest changes. It should organize the next batch, preserve the earlier record and ask for help when the input is unclear.
- 3.1
Register incoming assets
Give the proactive agent an intake prompt and approved file manifest. Have it classify audio, artwork and supporting records under one release identifier, keeping source filenames and versions.
Suggested time for this task: 2 hours in Full Course; 1 hour in Crash Course. Part of your class day, not extra time.- Practice result
- A release register with an intake queue.
- 3.2
Handle repeats and missing files
Run the proactive agent against a second batch containing a duplicate and a missing asset. Preserve completed entries, bound retries and route unresolved items to an owner.
Proactive agent practice. Create and test the release preparation proactive agent on one sample run. Name the role Release Desk and hand supported work to a Dot using approved release facts, contributor records and accessible audio previews. Define permitted actions and the return you expect; inspect the first result before giving it an ongoing responsibility.
Suggested time for this task: 2 hours in Full Course; 1 hour in Crash Course. Part of your class day, not extra time.- Practice result
- A repeat-run log with duplicate handling and stopped exceptions.
By the end of the day
A proactive intake agent that can process another batch without losing release history.
Review checkpoint
Check that repeated input does not create duplicate work or overwrite an approved version.
Day 04Keep credits and metadata consistent.
Have a metadata proactive agent review changed information on a set schedule. Its job is to compare records and prepare corrections; people resolve authorship, ownership and disputed credits.
- 4.1
Compare contributor records
Create a recurring check of the approved track sheet against incoming contributor updates. Retain source references and distinguish suggested corrections from approved values.
Suggested time for this task: 2 hours in Full Course; 1 hour in Crash Course. Part of your class day, not extra time.- Practice result
- A metadata comparison queue with evidence for each change.
- 4.2
Escalate conflicting credits
Introduce two conflicting contributor updates. Make the proactive agent stop the affected field, notify the designated reviewer and resume only after an approved resolution is entered.
Proactive agent practice. Connect the approved contributor record or supply a reviewed export. Set when the proactive role should check for changes and return conflicting credits to the release owner. It must not decide ownership or silently choose a name.
Suggested time for this task: 2 hours in Full Course; 1 hour in Crash Course. Part of your class day, not extra time.- Practice result
- A credit-exception record and a tested resume rule.
By the end of the day
A metadata proactive agent that keeps changes visible and disputed fields unresolved.
Review checkpoint
Confirm that an unresolved credit cannot become an approved fact merely because a later file arrived.
Day 05Turn listening notes into the next revision.
Coordinate the work around audio review. Use supplied LANDR comparisons and permitted audio examples; listeners judge sound while proactive agents maintain versions, notes and follow-up tasks.
- 5.1
Prepare the listening queue
Build a proactive agent that collects newly approved audio versions, listening references and delivery requirements into a review queue. Use supplied exports or an approved connection; do not infer sound quality from filenames.
Suggested time for this task: 2 hours in Full Course; 1 hour in Crash Course. Part of your class day, not extra time.- Practice result
- A versioned listening queue and review brief.
- 5.2
Track feedback to resolution
Have the proactive agent turn reviewer notes into revision requests and check their status on the next run. Block a request when feedback contradicts the artist’s recorded direction.
Proactive agent practice. Keep the listening-revision role available as feedback arrives. Link each accepted request to the right audio version and artist decision, then report unresolved revisions at the agreed checkpoint.
Suggested time for this task: 2 hours in Full Course; 1 hour in Crash Course. Part of your class day, not extra time.- Practice result
- A revision log linking each request to its audio version and decision.
By the end of the day
An audio-review coordinator that keeps human listening decisions attached to the right version.
Review checkpoint
Compare a request with the original listening note. Only a person can accept the musical result.
Day 06Keep campaign drafts aligned with the release.
Use a recurring proactive agent to prepare messaging as approved release facts change. Limit it to drafts so that a new date, title or asset cannot silently become a public announcement.
- 6.1
Prepare a dated content queue
Give the proactive agent approved copy, audience notes and release milestones. Have it draft a small announcement sequence and record which source facts each item uses.
Suggested time for this task: 2 hours in Full Course; 1 hour in Crash Course. Part of your class day, not extra time.- Practice result
- A campaign draft queue linked to release milestones.
- 6.2
Rebuild only affected drafts
Change the release date and one approved asset. Run the proactive agent again, preserving accepted work where valid and returning changed items for review.
Proactive agent practice. Confirm the campaign-preparation schedule and which release changes deserve an alert. Change the date and review affected drafts. Keep all claims grounded in approved release facts and leave publishing for approval.
Suggested time for this task: 2 hours in Full Course; 1 hour in Crash Course. Part of your class day, not extra time.- Practice result
- An impact report and revised drafts awaiting approval.
By the end of the day
A campaign-preparation proactive agent that responds to changes without publishing them.
Review checkpoint
Check that superseded dates and artwork no longer appear in the current review queue.
Day 07Assemble a release package for approval.
Bring the bounded proactive agents into a repeatable release-preparation workflow. Test whether it can pause, recover and explain what still prevents delivery.
- 7.1
Check the delivery manifest
Run a packaging proactive agent against a supplied delivery specification, current metadata and approved asset list. Produce a manifest without submitting anything to a distributor.
Suggested time for this task: 1 hour 40 minutes in Full Course; 50 minutes in Crash Course. Part of your class day, not extra time.- Practice result
- A checked delivery manifest with missing-item notices.
- 7.2
Test a delayed approval
Withhold an audio approval, then supply it on a later run. Keep the package blocked until requirements are met; bound reminders and retries so the workflow cannot loop indefinitely.
Proactive agent practice. Let Release Desk continue a cloud-capable assignment while you leave the chat. Inspect the result, block one input and test recovery. Then retire the responsibility: stop active delegates, cancel future schedules and retain the reviewed instructions. Recheck access and inputs before calling it back into service.
Suggested time for this task: 2 hours 20 minutes in Full Course; 1 hour 10 minutes in Crash Course. Part of your class day, not extra time.- Practice result
- A tested preparation workflow with a pause-and-resume record.
By the end of the day
A repeatable release workflow, delivery manifest and named approval queue.
Review checkpoint
Check that a technically complete package still waits for artistic, permissions and release approval.
MasterCourse - Capstone
Days 8–10 · MasterCourse only · Factory
Direct a Factory of proactive AI agent teams.
Coordinate multiple supervised proactive AI agent teams around a larger outcome. Define what each proactive AI agent team delivers, how work changes hands and where you approve the result.
Build a Factory of proactive AI agent teams around a shared outcome. Give each team accepted inputs, a named responsibility and a clear handoff. A Dot can coordinate continuing work and delegate bounded runs; each role does not need a separate personal Dot.
Day 08Give release proactive AI agent teams a shared operating plan.
Scale from individual proactive agents to multiple supervised proactive AI agent teams. Plan a small release sample that requires creative preparation, release information and campaign work to agree.
- 8.1
Assign the release proactive AI agent teams
Define Creative Assets, Release Operations and Campaign proactive AI agent teams, with at least two proactive agent roles per proactive AI agent team. Set their inputs, deliverables and limits around one shared release record.
Suggested time for this task: 1 hour 40 minutes in Full Course; 50 minutes in Crash Course. Part of your class day, not extra time.- Practice result
- A Factory proactive AI agent team map and shared release record.
- 8.2
Set the acceptance checks
Specify what each proactive AI agent team must receive before starting and what the next proactive AI agent team will accept. Include current asset versions, resolved metadata and named human decisions.
Proactive agent practice. Brief the Dot on Creative Assets, Release Operations and Campaign proactive AI agent teams. Test the credit, version and approval checks required before a handoff is accepted. Give each role a stable name and decide which responsibilities continue between cycles.
Suggested time for this task: 2 hours 20 minutes in Full Course; 1 hour 10 minutes in Crash Course. Part of your class day, not extra time.- Practice result
- A handoff table with acceptance checks and review owners.
By the end of the day
A release Factory plan connecting multiple proactive AI agent teams through explicit deliverables.
Review checkpoint
Every proactive AI agent team must have a distinct job and a downstream recipient. No proactive AI agent team can approve its own release decision.
Day 09Keep the proactive AI agent teams in step when plans change.
Run the proactive AI agent teams on a scoped release packet. Compress waiting periods for the exercise so you can examine a longer release cycle within the class.
- 9.1
Pass the release between proactive AI agent teams
Have Creative Assets supply a versioned asset packet, Release Operations validate the records, and Campaign prepare drafts from the accepted release facts. Log each acceptance or return.
Suggested time for this task: 1 hour 40 minutes in Full Course; 50 minutes in Crash Course. Part of your class day, not extra time.- Practice result
- An end-to-end handoff log for the sample release.
- 9.2
Resolve a late change
Introduce a revised master and a changed release date. Route the impact across all proactive AI agent teams, stop affected outputs and retain a clear record of the versions they replace.
Proactive agent practice. Introduce a late mix or credit change and ask the Dot to coordinate affected proactive AI agent teams. Inspect the returned asset record and campaign drafts for consistent updates. Check that waiting work resumes only after the required input or decision is accepted.
Suggested time for this task: 2 hours 20 minutes in Full Course; 1 hour 10 minutes in Crash Course. Part of your class day, not extra time.- Practice result
- A coordinated correction run with blocked and reapproved items.
By the end of the day
A tested proactive AI agent team workflow that exposes the consequences of a late release change.
Review checkpoint
Inspect whether every downstream proactive AI agent team received the same current facts before work resumed.
Day 10Approve the system for another release.
Complete an accelerated second run and judge the operating process. The goal is a reusable release-support system, not a promise to finish or distribute a release during the Capstone.
- 10.1
Tighten proactive AI agent team instructions
Use the first run’s errors to refine role boundaries, handoff checks, retry limits and escalation owners.
Suggested time for this task: 1 hour in Full Course; 30 minutes in Crash Course. Part of your class day, not extra time.- Practice result
- A revised Factory operating guide.
- 10.2
Run a second sample batch
Process a new, small release batch through all proactive AI agent teams. Compare completion, outstanding exceptions and approved versions with the expected manifest.
Suggested time for this task: 1 hour 20 minutes in Full Course; 40 minutes in Crash Course. Part of your class day, not extra time.- Practice result
- A second-run results record and release-readiness summary.
- 10.3
Record the release decision
Review the prepared package as the artist or release owner. Approve, return or stop each unresolved item; document who may authorize an actual delivery.
Proactive agent practice. Run a second sample release and inspect all versions, credits and outstanding permissions. Record the artist or release owner’s decision; do not treat preparation as permission to distribute. Retire the Factory’s active work and schedules, then rehearse a restart from its reviewed roles and a fresh approved input.
Suggested time for this task: 1 hour 40 minutes in Full Course; 50 minutes in Crash Course. Part of your class day, not extra time.- Practice result
- A human approval record and next-release checklist.
By the end of the day
A tested Factory of proactive release-support AI agent teams with a reviewed sample package and clear human release control.
Review checkpoint
Confirm that another operator can see what is approved, what remains blocked and what must happen before delivery.
Days 8–10 · MasterCourse - Capstone
A Factory with clear handoffs.
Prepare a scoped release packet across creative assets, release operations and campaign preparation, then prove the process can handle a revised version and a second batch.
Proactive AI agent team 1
Creative Assets
- Proactive agent roles
- Brief, Version coordinator, Listening-note
- Deliverable
- An artist-reviewed asset packet with versioned audio and revision notes.
- Handoff
- Pass accepted versions and unresolved creative questions to Release Operations.
- Acceptance check
- The brief, version names and recorded listening decisions agree; unresolved creative choices remain visible.
Proactive AI agent team 2
Release Operations
- Proactive agent roles
- Metadata, Contributor-record, Delivery-check
- Deliverable
- A checked release record and delivery manifest.
- Handoff
- Send accepted release facts to Campaign; return mismatched assets or credits to their owners.
- Acceptance check
- Required fields have sources, unresolved permissions questions are blocked and the asset list uses approved versions.
Proactive AI agent team 3
Campaign
- Proactive agent roles
- Messaging, Milestone, Copy-review
- Deliverable
- A dated announcement queue and audience-specific drafts.
- Handoff
- Return the campaign packet and source references to the release owner for final approval.
- Acceptance check
- Dates, titles and assets match the accepted release record; claims use approved artist facts.
Proactive AI agent teams work from one versioned release record. Approved changes trigger only affected work; scheduled checks follow up on outstanding tasks. Bounded retries, paused exceptions and explicit manual exports keep the process inspectable. Classroom runs compress waiting periods and use small supplied batches.
The artist and designated release owner retain listening, rights and delivery decisions. No proactive agent submits a release or publishes campaign material without a separate human approval.
The Capstone builds and tests a supervised prototype with sample cycles, revisions and exceptions. Longer projects continue beyond class; three days do not imply completion of a full production program.
A Factory that can carry work forward
Coordinate Creative Assets, Release Operations and Campaign as teams of proactive AI agents. The Dot follows one accepted release record across continuing preparation. A new mix, credit or date returns to every affected team; the artist and release owner approve delivery after the changes are reconciled.
Keep the approved brief, source versions and decisions in the shared handoff record. Notes help preserve context; they do not replace a checked record. Test a second cycle, a blocked handoff and recovery. Retire the Factory by stopping active delegates and future schedules; retain the reviewed roles for a later restart.
Your time commitment
How long is each class day?
You attend 10 live classes, one on each scheduled day. Choose Full Course or Crash Course for all 10 days. The times below include breaks.
Full Course
6 hours per day
More time to practice, ask questions and review your work.
Suggested plan for one day
- Lessons and hands-on practice
- 4 hours
- Review and questions
- 30 minutes
- Lunch break
- 1 hour
- Two short breaks
- 15 minutes each
10 class days × 6 hours = 60 hours totalIncludes all scheduled breaks.
Crash Course
2 hours 30 minutes per day
The same topics in shorter classes, with prepared examples and less practice time.
Suggested plan for one day
- Lessons and hands-on practice
- 2 hours
- Review and questions
- 20 minutes
- One short break
- 10 minutes
10 class days × 2 hours 30 minutes = 25 hours totalIncludes all scheduled breaks.
Lunch, breaks and review time are already included in each day. The task times in Daily detail fit inside the practice time above. Your trainer may adjust the plan; the start and end times shown with your selected dates are the ones to follow.
Choose your starting point
One progression. Three choices.
Intro teaches individually directed prompts. Intensive puts recurring work into proactive agents. MasterCourse connects the whole pathway and adds the Factory Capstone.
Intro
Learn to write music prompts, review a listening brief and check track information through a release-planning exercise.
Choose Intro to practice individual prompts for creative briefs, release copy and the information each track needs.
Intensive
Learn to build and supervise proactive agents that maintain release records, prepare drafts and bring missing credits, assets and approvals back to you.
Choose Intensive when you can already frame a task and want proactive agents to run recurring preparation work with clear limits.
Create and test proactive AI agents for release preparation. Name a role such as Release Desk, then hand suitable work to OpenAI Dots to keep assets, credits, listening revisions and campaign preparation aligned between reviews. Choose one run or a continuing responsibility, with approved connections, agreed reports and a clear way to pause or retire the work.
MasterCourse
Learn to connect music prompts and release proactive agents into a Factory of supervised proactive AI agent teams, with clear handoffs and artist approval before delivery.
Choose MasterCourse for all ten days, including the Capstone that connects creative assets, release information and campaign preparation across proactive AI agent teams.
Build a Factory of proactive AI agent teams for release preparation. Use a Dot to coordinate continuing work across their handoffs and return a current release record, affected drafts and outstanding artist or rights decisions. Test changing inputs, blocked work and a later restart. The artist and release owner approve creative decisions, rights and distribution.
Intensive is a five-day purchase, not a seven-day bundle. The three-day Capstone is available only inside the ten-day MasterCourse.
Live guidance · Continued reference
Come prepared. Keep what you learn.
Bring a computer, a reliable connection and a work example you are authorized to use. Sample or sanitized material lets you practice without introducing confidential source files.
Practice with guidance
Work through the assignments live, compare results and use trainer feedback to refine your prompts, proactive agent instructions and review standards.
Revisit your classes
Students have access to recordings of their classes in the members portal.
Specialist tools · Separate subscriptions
Tools serve the assignment.
Two specialist tools chosen for practical fit and an established learning ecosystem. Claude, OpenAI, Gemini and Open Source options support the prompt and proactive agent work. Specialist examples connect it to your field.
Suno
Generate musical sketches and review alternatives; editing and stem tools depend on plan.
Plan and access
Free plan; Pro $8/month or Premier $24/month, billed yearly.Free excludes commercial rights; paid rights remain subject to terms. Do not promise ownership, clearance or platform acceptance.
LANDR
AI mastering, sharing and distribution preparation support a music production workflow.
Plan and access
LANDR Studio is advertised from $8.25/month; confirm the current billing term.Confirm your plan includes the mastering, export and collaboration features used in class. Distribution is a separate approval step; rights and delivery requirements still need review.
Do I need my own software access?
Yes. Arrange full access to the required features before class, including suitable paid plans, usage credits and organization permissions. Software costs are separate from tuition. Free access may not cover every exercise.
How these tools support your course
Intro · Tasks
Use Suno to explore a few brief-led musical sketches and LANDR examples to compare mastering choices. Keep prompt versions, listening notes and eligibility questions attached to the sample work.
Intensive · Proactive Agents
Use permitted Suno and LANDR exports as inputs to the release workflow. Proactive Agents coordinate versions, review notes and metadata through supported connections or reviewed file handoffs; people make the musical decisions.
MasterCourse - Capstone · Factory
Carry the sample audio and release records through Creative Assets, Release Operations and Campaign proactive AI agent teams. Test a changed master, unresolved credit and delayed approval before the release owner reviews the package.
Vendor information checked September 29, 2026. Plans and limits can change. Proactive Agents use supported connections or approved exported inputs; specialist subscriptions do not imply universal proactive agent integration. Human approval remains part of publishing, releasing work and professional decisions.
OpenAI Dots · Proactive agents at work
Hands-on proactive agent and Dots work starts in Intensive. Check Dots availability, supported connections and your organization’s permissions before class. You authorize each app or browser session; Dots does not inherit all your logins. Subscriptions and usage charges are separate from tuition. Some specialist work needs a reviewed export or an online local application.
Cloud preparation can use approved release records and accessible preview files. A local audio workstation or private master library still needs its own authorized access and an available computer.
Before you choose
FAQ
Clear scope makes it easier to choose a course and arrive ready to work.
Which level should I choose?
Choose Intro to practice individual prompts for creative briefs, release copy and the information each track needs. Choose Intensive when you can already frame a task and want proactive agents to run recurring preparation work with clear limits. Choose MasterCourse for all ten days, including the Capstone that connects creative assets, release information and campaign preparation across proactive AI agent teams.
What does Factory mean?
A Factory coordinates supervised teams of proactive AI agents around a shared outcome. Each AI agent team has a defined responsibility, a deliverable and an acceptance check for the next handoff. You control permissions, review exceptions and approve release. The MasterCourse-only Capstone tests continuing cycles as well as individual runs.
Are recordings available?
Yes. Students can access recordings of their classes in the members portal.
How long is each class, and how many days do I attend?
This MasterCourse has 10 class days. Full Course lasts 6 hours each day, including lunch and two short breaks. Crash Course lasts 2 hours 30 minutes each day, including one short break. Choose one format for the whole course. Both cover the same topics; Full Course gives you more practice time. Check your selected dates for the exact start and end times in your time zone.
Which time zone will I see?
The class chooser detects your time zone automatically. Use Change time zone to select another location; the dates and hours update together.
Can Intro or Intensive tuition count toward MasterCourse?
The amount actually paid for Intro and/or Intensive can be credited once toward one MasterCourse enrollment within twelve months of each purchase. Intro and Intensive do not credit each other. No credit toward other programs, software or cash. Credit requests are reviewed against purchase records and eligibility; they are not an automatic checkout discount.
Full refund, transfer and credit policyWhat happens if I miss a day?
A missed day has a guaranteed place on the same curriculum day in a later cohort, free of charge, within twelve months of the original cohort's last scheduled day. After this window, new enrollment uses the then-published fee; day credits have no cash value and cannot buy a different curriculum day. An attended day may be repeated without charge within the same twelve-month window, subject to space. One free transfer of the whole seat or its unused days to a later cohort, in either published format, without a reason or a price increase, within twelve months of the original cohort’s last scheduled day. A day already consumed on one format is consumed on both; unused curriculum days are portable across dates and formats.
Full refund, transfer and credit policyWhat should I know before enrolling?
Full refund for a cancelled live program before its first scheduled session begins, including individual and group purchases and an approved MasterMind season. No refund after the purchased program starts, including dissatisfaction or absence, except for a session the provider fails to deliver. Statutory rights are unaffected. Partial attendance consumes the day under the published attendance rules. Read the full terms before choosing your class.
Full refund, transfer and credit policyWhen do I start using Dots?
Intro teaches individual tasks, clear prompts and review. Intensive teaches you to create proactive agents, test their work and hand supported responsibilities to OpenAI Dots. MasterCourse adds a Factory of proactive AI agent teams with shared records and coordinated handoffs.
Can the work continue after I close my phone or computer?
A Dot has its own cloud computer and browser. When the assignment, files and tools are available there, it can work while your phone or computer is off. Always-on means available to continue the responsibility; it may wait for a schedule, input or approval and remains subject to access and usage limits. Work using local files or applications still needs that connected computer online with the ChatGPT app open.
How do I stay in control over time?
Give the Dot and its assignments recognizable names, keep approved context current, and agree what deserves a report. It can surface missing input, access or decisions. To pause or retire work, check active delegates and saved schedules separately; pausing the main conversation does not stop them all. Review access and inputs before resuming.
What material can I use for the cloud exercises?
Use cleared sample audio and approved release information. Protect unreleased masters, private contracts and contributor details. A Dot does not establish ownership, clear samples or authorize voice imitation; the rights holder and release owner control those decisions and distribution.