LLM index
Symphony Control is the owner-operated control plane for Jira-triggered AI-agent runs.
It coordinates a narrow internal workflow for the Wentzel.ai monorepo: signed Jira events enter the control plane, eligible issues become D1 run records, workers claim scoped runs, and the control plane records write-back evidence. It is not a public product page, a general agent marketplace, or a claim of unattended production autonomy.
What exists today
- Receives signed Jira Cloud webhooks at POST /api/webhooks/jira, verifies HMAC and replay window headers, persists accepted events to D1, and treats issue text as untrusted data.
- Creates queued runs for issue-level Jira events only when the configured trigger label is present, the issue is in the trigger status, and no active run already exists for that issue key.
- Lets workers claim the oldest queued run through GET /api/runs/next with Authorization: Bearer WORKER_TOKEN, plus an optional signed single-use claim grant when WORKER_SIGNING_SECRET is configured.
- Accepts worker write-back through PATCH /api/runs/[id], validates legal state transitions, records run events, and performs Jira comments, links, labels, and transitions from the control plane.
- Provides owner-only operational views for recent run events, queue state, and arming configuration through BetterAuth-gated pages.
Accuracy boundaries
- Symphony Control is an internal control plane, not a public SaaS product or customer-facing signup flow.
- Workers do not receive authority to write to Jira directly; Jira side effects are centralized in the control plane.
- The default executor posture is mock/disarmed unless the owner changes arming config; kill-switch and loop-pause state can stop new claims or effective execution.
- The app stores non-secret arming config in its own D1 database. Arming secrets live in the canonical Secrets Vault and are decrypted only for authorized workers when effectively armed.
- It should not be described as fully autonomous, self-merging, or able to bypass human review. Background-agent rules require feature branches and PRs only.
Public references
- Overview - short public description of the control plane and dashboard entry point.
- Privacy - privacy policy for the Symphony Control surface.
- llms.txt - short text manifest for AI crawlers and retrieval systems.
- llms-full.txt - expanded text context with current capabilities and limits.