Back to corpus
architecturetechnical paper candidatescore 48

Symphony -- Stage 3 Expansion: Multi-Agent Architecture

> **Evolution:** Symphony -- Multi-Agent Orchestrator for Linear Issue Automation > **Stage:** 3 Expansion (Architectural Retrofit) > **Date:** 2026-03-07 > **Input:** Stage 2 Compound (8-step synthesis) + Stage 3 Master Plan (44 tasks) + Multi-Agent Research (970 lines) > **Engine:** Evo-Cubed Runner (Opus 4.6)

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

# Symphony -- Stage 3 Expansion: Multi-Agent Architecture ## From Codex-Only to Claude Code + Gemini CLI + Codex as Interchangeable Backends > **Evolution:** Symphony -- Multi-Agent Orchestrator for Linear Issue Automation > **Stage:** 3 Expansion (Architectural Retrofit) > **Date:** 2026-03-07 > **Input:** Stage 2 Compound (8-step synthesis) + Stage 3 Master Plan (44 tasks) + Multi-Agent Research (970 lines) > **Engine:** Evo-Cubed Runner (Opus 4.6) The original monorepo has `packages/codex-client/` as the sole agent integration. This package is replaced by `packages/agent-adapters/`, which contains a unified interface, three adapter implementations, and an event normalization layer. The key constraint is preserved: `agent-adapters` is a package, not a service. It has no dependency on `linear-client`, `workspace-manager`, or `state-machine`. The orchestrator in `symphony-daemon` wires these together. This means each adapter is independently testable. Codex has no npm dependency -- it uses auto-generated types from `codex app-server generate-ts` committed directly into `types/codex-types.ts`. Gemini has no npm dependency -- it uses manually defined types for the NDJSON stream format.

Promotion decision

What has to happen next

Promote into a technical note or architecture paper with implementation anchors.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.