Design is now approved before any infrastructure code is written (ADR-0005). A new target-architect Specialist produces one graph of Elements, Relationships and Checks; the diagram is rendered from it, deployment guidance must account for every Check, and validation gives a verdict per Check. Requirements, components, products and recommendations carry ids in data files, and a submission with a gap in the Requirements chain is refused. Also in this commit: - Customer cases group Executions, with an intent history per case - lesson candidates are captured when an Execution ends - evaluation gains chain, verdict, judged and interactive checks, and per-case thresholds - Terraform providers are cached between checks - the requirements analyst proposes defaults instead of asking - the legacy-baseline case and the checks that only read it are removed - ADR-0006 (Change requests) accepted; ADR-0004 and ADR-0007 proposed - plans for iterations 4 to 7 under .agents/plans/ Unproven with a real model: no evaluation run has completed on this design. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2.6 KiB
2.6 KiB
status, supersedes
| status | supersedes |
|---|---|
| accepted | ADR-0001 |
LangGraph holds Execution state; ADK agents reason and act
An Execution is a hierarchy of ReAct agents shaped by the dependencies between Deliverables (ADR-0002).
- LangGraph holds the Execution. A LangGraph
StateGraphholds the dependency graph and each Deliverable's state. It checkpoints after every step and pauses withinterrupt()whenever the user must answer or approve. This follows the KAB workflow standard and the platform'slanggraph-workflow-agent. - ADK agents reason and act. The Orchestrator and every Specialist is an ADK
LlmAgent, each running its own ReAct loop, with aSkillToolsetfor progressive Skill loading. This follows the platform'sgoogle-adk-base-agent/app/skills_integration.py. - Agents sit behind one interface. Each agent runs behind a single agent-runtime interface, so LangChain Deep Agents can be added as a second implementation without touching the graph.
The dependency graph is declared as data in code. The Orchestrator picks what to do next through tools that refuse work whose dependencies aren't met. Dependencies are guaranteed by code, while ordering and parallelism are the model's choice.
Under review (2026-10-07). ADR-0007, proposed, would have the Orchestrator decide with Jev and run no language model. If accepted, it replaces "the Orchestrator ... is an ADK
LlmAgent" above and reverses the third option rejected below. Specialists are unaffected.
Considered Options
- ADK end to end (root
LlmAgentwithsub_agents/AgentTool, and ADK sessions for pauses): rejected. It departs from the KAB workflow standard, and LangGraph's checkpointedinterrupt()is the proven platform path for resumable user Approvals. - Deep Agents end to end (
create_deep_agent(skills=, subagents=)): viable, and it compiles to LangGraph. It was deferred rather than rejected: ADKSkillToolsetalready has working prior art on this platform, and Deep Agents stays reachable as the second implementation of the agent-runtime interface. - Code runs the dependency graph with no Orchestrator model: rejected. The top level wouldn't be ReAct, and the Skill's conversational flexibility (such as skipping work the user says is already approved) would need hand-coding.
Consequences
- There are two frameworks in one process. Framework types stay inside the agent-runtime implementation and never appear in graph state.
- ADK Skills are Experimental (Python ≥ 1.25.0), so pin the version.