ableton-live-mcp AGENTS.md

Open Orchestra Runtime Bootstrap

Runtime target: Codex. Reference Open Orchestra from AGENTS.md so local CLI work follows workflow gates.

Non-Negotiable Runtime Rules

These rules are non-negotiable. Follow them in every conversation and every work block:

• Use Orchestra for all project work: planning, implementation, fixes, reviews, QA, release, CI, research, and documentation.
• Do not edit files, run implementation work, or dispatch agents before a matching Orchestra task exists and a workflow run is active.
• Always run the runtime health preflight, inspect active tasks, and validate pre-run context before work.
• If a gate is paused, stop and wait for explicit user approval before continuing.
• Record real evidence: commands, files, outputs, logs, screenshots, traces, or explicit deferred-risk rationale.
• Never treat simulated handoffs, generated summaries, or workflow state alone as proof of completed QA.
• Never push, tag, publish, or deploy without explicit user instruction.

Use Open Orchestra as the local control plane when .agent-workflow/ exists. The active LLM runtime is the parent agent. Orchestra renders spawn requests and records lifecycle; it does not call provider APIs directly.

Orchestra Workflow — Required for All Work

Every piece of work — feature, bug fix, architecture decision, stack definition, PO refinement, or research spike — MUST go through the Orchestra workflow. Do not start any work without a registered task and a running workflow.

Managed Work Routing for External Runtimes

External runtimes and provider-backed agents — including Claude, Codex, Cursor, VS Code, Windsurf, OpenCode, and generic LLM runners — must infer managed work intent from natural language. When the user asks to implement, fix, review, release, deploy, plan, research, investigate, spike, groom, estimate, validate, QA, or document work in a project with .agent-workflow/, route the request through Orchestra instead of executing ad hoc. The required routing sequence is:

1. Load workspace state with orchestra health --json and orchestra task list --json --status pending,blocked,in_progress.
2. Reuse the matching active task when one exists; otherwise create or refine a task with orchestra task add before doing implementation, research, or provider calls.
3. Record the estimate and run orchestra validate --pre-run --task <ID> --json; if context is missing, resume or register the workflow before editing files.
4. Start or resume the workflow with orchestra workflow run --task <ID> --gates phase or orchestra workflow run --task <ID> --resume <run-id>.
5. If acceptance criteria, sizing, or gate approval is missing, stop and record clarification/review instead of bypassing the workflow. This hardening is for external runtimes. The local provider/backbone path may stay tightly coupled to Orchestra internals, but it must not be used as a precedent for Claude, Codex, Cursor, VS Code, Windsurf, OpenCode, or generic provider behavior.