Two-directional comparison. Part 1 scopes to Symphony's feature set (github.com/openai/symphony — SPEC.md + the Elixir reference implementation, analyzed from a local checkout 2026-07-12), rating Cascadian against it. Part 2 reverses the question: a strict tally of Cascadian's feature set rated against Symphony, with coverage percentages. Ratings throughout: ✓ has it, ≈ partial/different mechanism, ✗ absent. In Part 1, * = coded in Symphony but undocumented in any of its doc surfaces (easter egg).
Architectural frame: Symphony is a standalone daemon that polls an issue tracker (Linear) and drives an external coding agent (Codex app-server) in isolated per-issue workspaces. Cascadian is an in-harness process plugin — the orchestration (PE/ONP), quality gates, and issue lifecycle run inside Claude Code itself. Many ✗ rows are architecture, not absence of thought.