Artist
Provides intent, story, audience, and approval boundaries.
A practical map for where each generated Markdown file belongs before a human approves release, licensing, or distribution work.
Provides intent, story, audience, and approval boundaries.
Chooses Basic, Medium, High, Hyper, or Max and maps platform asset requirements.
Organises songs, stems, artworks, lyric files, video seeds, and variants.
Normalises titles, credits, moods, themes, audience fit, and semantic tags.
Captures contribution ratios, tool use, human curation, and review checkpoints.
Summarises rights questions, collaborator status, samples, and sync review notes.
Maps contracts, T&C, policies, data rules, and questions for qualified advice.
Checks release readiness and compares the pack against platform requirements.
Receives clearer metadata, provenance, and context for review and discovery.
Returns performance and audience signals into the artist-controlled catalogue.
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.
Best when the release needs platform sizes, formats, tiers, merch, and strategy boundaries.
PackBest first document for organising a song, album, or video release.
HITLBest when the project needs transparent human and AI contribution language.
LegalBest when contracts, T&C, data rules, subscriptions, or deletion logic are unclear.
BriefBest when Codex, OpenClaw-style tools, or a human reviewer needs the next task.