Shea Symphony

Shea Symphony: An opinionated and extended Rust implementation with GUI of OpenAI Symphony orchestration system to make it also work for powerusers or small engineer teams that want to build AI-native engineering workflows in a responsible and manageable way. It adds higher configurability, observability, recoverability, and also new workflow nodes including issue forge, team-aware claiming and processing with boundaries, guided human review and approval, reflective backlogging, docs, improve code base, HALO, etc.

Operator cockpit

The Shea Symphony App keeps lane queues, human decisions, local worktrees, and issue-level evidence visible in one foreground workspace.

Shea Symphony helps an operator:

• shape rough intent into tracker-backed, executable issue contracts;
• move implementation through separate Main, Agent Review, Human Review, and Merge boundaries; and
• understand and recover interrupted work from durable evidence instead of reconstructing an agent session from scratch.

More App views

The Lanes view brings the current human queue, active lane work, and local issue worktrees together.

The issue view connects tracker state with worktree provenance, handoff links, and lifecycle evidence.

Public entrypoints

• Use the global setup-shea Skill to onboard or reconcile a repository. It installs an immutable release-selected contract while leaving the resulting repository resources customizable. setup-shea itself is not vendored into the target repository.
• Use the Shea Symphony App as the normal operator surface. The Legacy CLI is an internal compatibility adapter used by the App, Skills, and bounded recovery paths; it is not the normal user interface.
• Start a Skill from Codex or from Claude Code. .agents/skills/ holds the one authoritative body of each Skill; each harness only adds discovery metadata, agents/openai.yaml for Codex and a thin delegating entry point under .claude/skills/ for Claude Code. The lane contract, permissions and evidence are identical from either side.
• OpenWiki runs on the installed openwiki executable; no copy is vendored or pinned here. Its Skill is tracked for both harnesses, but the MCP server registration is machine-local like .codex/config.toml already was, so each clone runs openwiki integrations install codex and openwiki integrations install claude once. That server makes no model calls, so a refresh uses the inference of whichever session runs it.

Documentation

• OpenWiki is the public documentation and navigation surface. Its freshness metadata must be checked before treating a generated page as current.
• docs/README.md routes coding agents to the smallest authoritative repository context for a task.

OpenWiki is derived. Source code, tests, workflow configuration, repository contracts, accepted decisions, and the live tracker remain authoritative for their respective facts.

Runtime transition

The protected 2606 MVP remains a behavior and recovery baseline while 2607 replaces its hand-rolled orchestration with Temporal. On current main, the default shea-symphony executable is the Temporal worker. The App temporarily uses the separately identified shea-symphony-legacy sidecar for compatibility operations; see docs/legacy-runtime-distribution.md.

The active design and dated implementation snapshot live under docs/milestones/2607-hardening/.

Development checks

cargo fmt --check
cargo clippy --all-targets --all-features -- -D warnings
cargo test
npm --prefix app test
npm --prefix app run check