Describe a piece as sixteen numbers per bar -- density, register, tension, syncopation, dynamics and the rest -- so a model can perceive what is written.

Apply a bandleader's directive JSON to a piece or an ensemble session and return the result as data: the directives as they were read, what the arrangement was before and after, and the sixteen features per bar of each. Use conduct_score instead when you want the timing report in prose.

Compile notation to MIDI and audio, returning the arrangement summary and any diagnostics. Pass either a path or inline content.

Apply a bandleader's directive JSON to a piece and report what it did to the ensemble's timing: how the arrivals moved together and how far each player's hands moved to keep them there.

Read the conductor's directive vocabulary -- the JSON a bandleader sends, which actions the timing layer acts on, and what the windows and targets mean. Call this before writing directives for the first time in a session.

Claim one voice of a session. A voice has one owner at a time, so claiming is how agents avoid choosing the same part. Returns everything needed to start writing.

Release a voice you hold so another agent can take it.

Read the session's change log, oldest first. This is how a joining agent finds out what has already happened.

Open a shared session several agents can write to, or reopen one that exists. Sets the key, tempo, metre and form every part is written against.

Read a session in one call: key, tempo, metre, form, which voices exist and who holds them, what every voice plays in the bars you are about to write, your own part, the version to write against, and what has changed recently.

Merge the parts and compile the session to MIDI, and optionally audio.

Report what a listener on the stage actually hears: each voice's distance, speech time, propagation delay and the moment its player has to act, plus the spread at the chosen listener and at every other one.

The short view of a session: version, voices, who holds what, bar count and whether the merged score still compiles. Omit the name to list sessions.

Write your voice's part. The notation is parsed and checked against the session header before anything reaches disk. Pass the base_version you read; if the voice has moved on the write is refused and you are given the current part to rebase onto.

List files in the working directory.

Read the TapScript notation reference. Call this before writing notation for the first time in a session.

Report what this machine can do: platform, optional libraries, soundfonts, MIDI ports, audio playback, network. Use it before choosing how to render or connect.

Read a text file from the working directory or the project.

Read one file from the bundled notation library, by name or title.

Append a line to the build journal, recording a decision and why it was made.

Search the bundled notation library for reference material by title, key or style.

List the instrument speech profiles a [Stage] block can name, with how long each takes to sound and how far into the attack the ear places it.

Read how to write a [Stage] block: positions, listeners, speech profiles and feel. Call this before writing arrival-centric timing for the first time in a session.

Transpose a notation file to another key, writing the result next to it.

Run the project's specs and report what passes and what fails. Use this after making a change to check whether it worked.

Write a text file into the working directory, creating parent directories.

Write TapScript notation to a .tap file. The notation is parsed first and the result reports any problems, so use this rather than write_file for music.