Agent pipeline map.

A practical map for where each generated Markdown file belongs before a human approves release, licensing, or distribution work.

01

Artist

Provides intent, story, audience, and approval boundaries.

human sourceauthority
02

Asset Guide

Chooses Basic, Medium, High, Hyper, or Max and maps platform asset requirements.

strategyformats
03

Creation Agent

Organises songs, stems, artworks, lyric files, video seeds, and variants.

assetsrelease pack
04

Metadata Agent

Normalises titles, credits, moods, themes, audience fit, and semantic tags.

schemarecommendation
05

HITL Provenance Agent

Captures contribution ratios, tool use, human curation, and review checkpoints.

transparencyAI disclosure
06

Licensing Agent

Summarises rights questions, collaborator status, samples, and sync review notes.

rightsnot legal advice
07

Legal Clue Finder

Maps contracts, T&C, policies, data rules, and questions for qualified advice.

fine printsource trail
08

Distribution Agent

Checks release readiness and compares the pack against platform requirements.

validationsubmission prep
09

DSP / Streamer

Receives clearer metadata, provenance, and context for review and discovery.

ingestiontrust
10

Feedback Loop

Returns performance and audience signals into the artist-controlled catalogue.

learningconsent
Docs

What to generate first

Start with the document that matches the uncertainty. If the campaign size is unclear, make an asset guide. If the asset set is messy, make a release pack. If AI contribution is unclear, make a provenance note. If the confusion lives in contracts or terms, make a legal clue query. If a person needs to do work next, make an agent brief.