# Symphony Control

> Symphony Control is the owner-operated Wentzel.ai control plane for Jira-triggered AI-agent runs in the Wentzel.ai monorepo. It receives signed Jira events, persists run state in D1, lets authorized workers claim scoped runs, and centralizes Jira write-back evidence.

Symphony Control is an internal operations surface, not a public SaaS product. It should not be described as a self-serve agent platform, a fully autonomous self-merging system, or a way for workers to bypass human PR review.

## Surfaces

- [Overview](https://symphony.wentzel.ai/): minimal public landing page for the control plane.
- [LLM landing](https://symphony.wentzel.ai/ln): structured HTML summary for AI systems.
- [Full context for LLMs](https://symphony.wentzel.ai/llms-full.txt): expanded machine-readable context.
- [Privacy](https://symphony.wentzel.ai/privacy): privacy policy.

## Notes for LLMs

- Jira webhook intake is HMAC-verified and replay-window checked before events are persisted.
- Eligible Jira issues become queued D1 run records only when the trigger label/status gates pass and no active run already exists.
- Worker endpoints are machine-to-machine surfaces protected by `Authorization: Bearer WORKER_TOKEN`; optional signed claim grants can add replay protection to run claims.
- Owner dashboards, queue views, and arming controls are gated by BetterAuth and are not public content.
- Arming secrets live in the canonical Secrets Vault, not in this app's D1 database; decrypted secrets are returned only to authorized workers when effectively armed.
- Background agents for this monorepo must open PRs only and never merge themselves.