composer-studio.git · README.md

revision 38616459632dd2659b5f331f871546e06a9cc2a1 · complete file

# Composer Studio — Score + Script Agent Design

Composer Studio is a two‑pane score + screenplay surface where LLM reasoning is expressed through **instruments**, not generic chat. The runtime implementation lives in the FountainKit workspace and existing Fountain Coach services; this repository documents how those pieces fit together and is structured to be a valid Swift Package Manager root when code is added later.

- Left pane: a manuscript‑style score page backed by a `ScoreInstrument`.
- Right pane: a screenplay page with ACT/Scene navigation backed by a `ScriptInstrument`.
- Additional surfaces: a cue planner and chat view, backed by dedicated instruments.

Baseline visual mock:

![Teatro Possibile mock](Teatro-Possibile-Mock.jpeg)

The **agent** that drives reasoning is `fountain.coach/agent/composer-studio/service`. It runs in the control plane (gateway + planner + function‑caller + awareness + tools‑factory + bootstrap) and uses FountainStore as its memory and prompt/facts store. This repo keeps the design, not the prompts or model weights.

## Repository layout

- `AGENTS.md` — root guide and index for all agent‑facing documentation.
- `agents/AGENTS.md` — agent identity, corpora layout, and Teatro prompt/facts locations in FountainStore.
- `instruments/AGENTS.md` — Score, Script, CuePlanner, and Chat instruments with their PE properties and intended behaviours.
- `services/AGENTS.md` — HTTP service surfaces (`composer-score`, `composer-script`, `composer-cues`, chat endpoint) and their OpenAPI operation shapes.
- `integration/AGENTS.md` — how existing services (baseline‑awareness, planner, function‑caller, tools‑factory, bootstrap, gateway) make Composer Studio a reasoning agent.
- `ui/AGENTS.md` — baseline UI layout derived from the Teatro Possibile mock (score left, script right) and where instruments attach.
- `openapi/AGENTS.md` — where the authoritative OpenAPI specs live in `FountainSpecCuration` and how they must be kept in sync with this design.

All `AGENTS.md` files are written for humans first, with just enough structure for agents to navigate. They are the canonical narrative for how Composer Studio should behave; OpenAPI specs and FountainStore corpora are the authoritative sources for machines.

## SwiftPM / Swift 6 notes

This repo is prepared to act as a SwiftPM package root for future implementation work:

- `.gitignore` is configured for a Swift 6 SwiftPM project (avoids committing `.build`, `.swiftpm`, Xcode artifacts, and local caches).
- When a `Package.swift` manifest is added, standard commands apply:
- `swift build` — build Composer Studio and its targets.
- `swift test` — run any tests added to the package.

Until then, treat this repository as documentation and design source only. Runtime code continues to live in the FountainKit workspace and related Fountain Coach packages.\n+