composer-studio.git · AGENTS.md

revision 38616459632dd2659b5f331f871546e06a9cc2a1 · complete file

# Composer Studio — Agent Guide (Repository Home)

This repository is the design home for the **Composer Studio** agent and app: a two‑pane score + screenplay surface where LLM reasoning is expressed through instruments, not generic chat. The runtime implementation lives in FountainKit and the core services (planner, awareness, function‑caller, tools‑factory, bootstrap) live in existing Fountain Coach repos; this repo documents how they fit together.

The app baseline is a page of manuscript paper on the left and a screenplay page on the right. Instruments sit behind each pane and behind the chat surface. The agent runs in the control plane; this repo defines how the app, instruments, OpenAPI surfaces, and FountainStore corpora hang together.

## Map

- `agents/AGENTS.md` — agent identity, corpora, Teatro prompt + facts conventions.
- `instruments/AGENTS.md` — Score/Script/CuePlanner/Chat instruments and their PE properties.
- `services/AGENTS.md` — composer‑* service surfaces (score, script, cues, chat) and their OpenAPI operations.
- `integration/AGENTS.md` — how existing services (baseline‑awareness, planner, function‑caller, tools‑factory, bootstrap) become tools for this agent.
- `ui/AGENTS.md` — UI baseline, layout and relationships between panes and instruments.
- `openapi/AGENTS.md` — where the authoritative OpenAPI specs live in the FountainAI curation repo.
- `testing/AGENTS.md` — MRTS (MIDI Robot Test Script) and TDD workflow for Composer Studio.

The implementation plan and Definition of Done for Composer Studio live in `PLAN.md`. Keep `PLAN.md` and the AGENTS documents aligned: when a milestone completes or scope changes, update both the plan and the relevant AGENTS sections.

Each document is written for humans first, with enough structure for agents to navigate. No prompts or facts are authoritative here: they live only in FountainStore; this repo references their locations and expected shapes.