Agent guide
Song Planner is the durable workspace for AI-assisted music creation.
The app stores the human-owned plan, source notes, lyrics, prompts, generation attempts, and review state. Assistants should use their own reasoning, browser, and approved external tools for research and creation work, then save structured results back into Song Planner.
Account expectation
Private planner data requires a signed-in Clerk account. V1 browser UI writes are authenticated; remote MCP/OAuth is planned but should not be assumed until a verified endpoint and client setup are published here.
Creation modes
- Exact public-domain lyrics
- Adapted public-domain lyrics
- Scripture or idea-based songs
- Complete originals
First workflow
Open the planner, choose a project, create or open a song plan, then save research, lyric drafts, prompts, and generation attempts as separate durable records.
Agent boundary
Song Planner stores memory and review state. The assistant handles synthesis, drafting, browser work, and external tools only when the user has access and explicitly directs the action.
Safety defaults
Do not export private workspace data, claim unverified copyright status, perform destructive changes, or automate external accounts without user approval.
Planned MCP tool families
The remote endpoint is not live yet. The public contract draft defines names, idempotency keys, auth expectations, and verification gates for the next implementation slice.
- get workspace, project, and song-plan context
- upsert song plans, research notes, lyric drafts, and prompt attempts
- log generation attempts and source checks
- save a complete creation result in one idempotent call
- read genre recipes from the encyclopedia