Assign the release proactive AI agent teams

In the Intensive you ran single proactive agents (agents that keep working on a written method while you're in the booth), one per chore: intake, credits, listening, campaign drafts and packaging. Each one did its job well. But a release is rarely damaged inside a single job. It's damaged between jobs, in the handoffs.

The common failures look like this:

• The wrong bounce goes up. Intake logged the revised master correctly, but packaging still pointed at "final two".
• A player is left off the credits. The session bassist who replaced the hummed part is on the take sheet but never reached the credits sheet.
• An old date survives. The release moves a week, and the old date stays live in three posts and a pre-save link.

In each case, every agent was right about its own files. Nothing kept them in step. That's the problem this Capstone solves. You'll organize your agents into a Factory: supervised agent teams that work from one shared record, with clear handoffs, and nothing delivered until the artist approves.

Jimmy Jam is a five-time Grammy-winning producer and songwriter who chaired the Recording Academy's board from 2007 to 2009. He compares AI to the arrival of cars. Once cars arrived, people paved roads, painted lanes, added guardrails and posted speed limits. He argues AI needs the same guardrails and guidelines. The technology is wonderful, but it can be used in right and wrong ways. His central concern, in his words: "my big thing is permission." Nothing should be used without it, samples included, and people whose work goes in should be paid.

In the Factory, this becomes three rules:

• Lanes: each team has its own job and doesn't do another team's.
• Guardrails: every handoff between teams has a check before the next team accepts the work. You'll write these in the next lesson.
• Permission and payment before use: no voice, sample, credit or asset moves forward until consent and payment terms are on record.

Example: Campaign wants to quote a featured singer's line in a teaser. That's outside its lane until the singer's consent is recorded.

Your single agents now become three teams. Each team has at least two roles, so one role can check the other's work inside the lane.

Creative Assets knows which master is current and what it replaced. It handles version intake and the listening queue, set against the artist's written direction (for example, the first-verse note: voice and guitar only, close enough to hear the breath).

• Version keeper: logs every new master as a new version and never overwrites the approved one.
• Listening-queue keeper: queues new versions beside the artist's note for the artist's ear.

Release Operations checks credits, splits, version names and the distributor spec. Composition credits (who wrote) stay separate from recording credits (who played and engineered).

• Credits and splits checker
• Spec and packaging checker

Campaign writes only from facts the other two teams have accepted, and every draft cites the facts it uses. Nothing publishes.

• Drafter
• Fact checker: confirms each date, title and name against the record.

Your role names can differ. What matters is that each lane is distinct.

A lane only works if it leads somewhere. Each team needs a named downstream recipient: the team or person who receives its output next. Without one, finished work sits in a folder and nobody knows whether it was taken up.

A typical chain for a single:

• Creative Assets hands the current master, its version name and what it replaced to Release Operations. It also passes the accepted asset list (master, artwork) to Campaign.
• Release Operations hands accepted credits, version names and the release date to Campaign, and the checked package to the release owner.
• Campaign hands its cited drafts to the artist and release owner for review.
• The artist and release owner approve, return or stop each item.

Notice that the chain ends with people, not with a team. In your plan, write each recipient by name or role, for example "Release Operations: credits and splits checker" or "Maya (release owner)", not "the next team".

The teams share one release record: the single source of truth for the release. Each team reads from it and writes back to it. No team keeps a private copy of the facts. If Campaign kept its own date in a notes file, that copy would be exactly where an old date survives.

Tom Gray, songwriter and chair of the Ivors Academy, describes every nomination and award as "an act of attribution": a public statement that named people made the work, people who can be identified, credited and paid. Your release record keeps that attribution every day, not just at awards time.

Your first version should include at least:

• Who wrote: composition credits and agreed splits
• Who played: recording credits, including session players
• Who consented to what: voices, samples, likeness, with evidence
• Who called the take: who chose the approved master, and when
• Current facts: current master and what it replaced, version names, release date, status of each item (accepted, open, frozen)
• Open fields: anything unsupported, each with an owner

A field nobody has confirmed stays open, with an owner. It never gets filled in by guessing.

Teams prepare. People decide. No team approves its own release decision. Creative decisions, rights decisions and distribution decisions belong to the artist and the release owner. A team can accept a handoff, meaning it agrees the work matches the record. It can't approve the release.

Example: Release Operations finds that the publisher's split sheet contradicts the agreed share. It freezes the split and notifies the release owner. It doesn't choose the "right" split, even if one file arrived later. A file doesn't win by arriving later.

The second guardrail is access that matches the lane. Each team should reach only what its job needs:

• Creative Assets reaches the masters and the artist's written direction.
• Release Operations reaches the credits, splits and distributor spec.
• Campaign reads accepted facts from the record. It doesn't need private contracts, unreleased stems or contributors' personal details.

This protects unreleased masters, private contracts and contributor details. If a team asks for access outside its lane, treat that as a signal to recheck the plan.

Now plan the small sample release packet you'll run through the Factory on Days 9 and 10. Use your own material or the course's, and only material you have permission to use. Keep it scoped to one single, which is enough to test without trying to finish a real release.

A good sample forces all three teams to agree. For example:

• Two master versions: the approved one and a revision (Creative Assets)
• Artwork, ideally with one duplicate file (Creative Assets)
• A credits and splits sheet with a session player and one split you'll later dispute (Release Operations)
• A distributor spec that asks for an instrumental (Release Operations)
• A campaign draft with a date and a pre-save link (Campaign)

Notice the dependencies. Campaign can't confirm its date or credits until Release Operations accepts them. Release Operations can't name versions until Creative Assets says which master is current. If one team could finish without the others, the sample is too easy to test handoffs.

Write your plan: teams, roles, recipients, the first release record and the decisions reserved for the artist and release owner.