Files
solution_architecture_agent/docs/adr/0001-langgraph-orchestrates-phases-not-google-adk.md
Jonathan Boniface c84dbdea20 feat: the solution architecture agent on the shared Execution engine
The reference agent's subject, cloud solution architecture, as an agent in
the operating model agent's pattern: the Execution engine (from
orchestration_engine) and one Workflow in app/solution_architecture,
built for the settings and provider bundle by assembly.workflow_for.

Copied from gcp_solution_architecture_agent at 8b397cd without its own
engine: its role files, Skills, provider bundle, ADRs, vocabulary, scripts
and evaluation datasets. The image takes the engine from a named build
context and installs Terraform. It is called through the Orchestration
engine, and its files are what the operating model agent digests.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-21 19:49:28 +01:00

1.5 KiB

status
status
superseded by ADR-0003

LangGraph orchestrates Phases, not Google ADK

Phases are orchestrated by a LangGraph StateGraph, as the KAB Workflow Agent standard (kyndryl-agent-builder/docs/KAB_WORKFLOW_AGENT_IMPLEMENTATION_GUIDE.md) requires, rather than by Google ADK Runner/LoopAgent. The earlier "ADK" orchestration was a local compatibility layer that never used the real google-adk package, so it added a pretend seam with one adapter and diverged from the platform standard; we deleted it. Real ADK remains welcome inside a Phase (e.g. an LlmAgent for LLM-driven design) — just not as the thing that sequences Phases.

Reopened (2026-09-15). ADR-0002 makes Skills, loaded by a framework's own skill runtime, the portable unit of behaviour. This ADR assumed our code sequences the Phases. If the Skill sequences them instead, the choice here reduces to which skill runtime to wire first, and "ADK only inside a Phase" no longer holds. Still true regardless: the compat stubs are fiction and should go.

Considered Options

  • Real google-adk as orchestrator: rejected; departs from the KAB workflow standard and would require async event-stream plumbing for no capability LangGraph lacks (conditional edges cover the Review round).
  • Plain in-process pipeline, no framework: rejected; neither KAB template uses it, and LangGraph already gives us conditional routing and a path to checkpointing if a human approval gate is added later.