A scope spec is a YAML file of what the customer wants and the facts a design
depends on, complete or partly filled. It sits beside the Intent, which stays
in the customer's words.
- skills/scoping holds a provider-neutral catalogue of 63 fields; the Cloud
provider's bundle supplies the values it allows for the fields left to it.
- app/scope.py reads a spec against the catalogue with no model: it refuses an
unknown field or a value of the wrong type, and yields what is stated, what
is left to the agent, what is unknown and how pressing each gap is. A field
may say ask, decide or not_applicable.
- ExecutionEngine.start(scope=...), /generate, A2A metadata and evaluation
cases accept one. Its statement is the request, its engagement reference
names the Customer case, and its run options apply. A pre-approved start is
refused when an essential field is not settled.
- The spec as supplied is kept unaltered beside a completed copy with
assumptions, gaps, provenance, readiness and a status.
- Every Specialist is shown the spec and given the Skill: a stated choice
binds, exclusions are out of scope.
- Covers workloads and platform foundations; case-08-landing-zone starts from
a benchmark spec.
Plans for scoping (iteration 9) and the work breakdown structure (iteration
10, nothing built), and the design spec they come from. Not run with real
models.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- A Check met through a module is met by a value in the code: the modules
Skill tells the author to set every input a Check depends on.
- scripts/check-terraform-modules.py reports catalogued modules with a newer
version, and watched modules that can now be used with the pinned provider.
- L-07 no longer mentions a low-carbon location, which led to a Check about a
region's carbon score that code cannot show. Reworded with the owner's
approval.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Evidence was grouped only by the kind of problem, and a group gets one lesson,
so what kept recurring inside "validation proposed a Check" could not be
seen. A proposed or unimplementable Check is now also counted under each
provider setting or resource type it names; a subject seen in two or more
Executions is its own group and reaches the curator past triage.
Over 32 Executions that gave five proposals. The owner approved three, now
published: L-07 location Checks, L-08 Cloud SQL backup encryption, L-09
backend service capabilities. L-10 is held for more evidence and L-11
rejected.
Also: retiring a lesson marks its proposal, so publish no longer brings a
retired lesson back. L-04 had returned to the Skill that way.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- An Execution's files are written as each Deliverable is submitted, marked
in_progress, so a killed process or one waiting for its user leaves them on
disk. A write removes files an earlier write left that it no longer has.
- A question about delivered work is answered from that Execution's solution
guide by the reply writer; a question about the service is answered as
before. Nothing is started for either.
- Lessons: prove writes only for lessons the Skill holds; the Skill records
the vendored Skill versions the lessons were read against, status names any
that changed, and a test fails until they are reviewed.
- Four more code patterns: Firestore, BigQuery, Eventarc and GKE.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Schema review: a dotted path is judged only when it starts at a name the
resource type has, so a database flag or a service name is no longer read
as a missing setting. Lesson L-04, which worked around that, is retired.
- Skill routing: in a Change request the question says what changed.
- Evaluation: a case may list code_standards the infrastructure code must
meet; case 06 checks its overlay's regions, naming and labels.
- Model tiers (iteration 5 step 6): a lighter model for a role's first
attempt, named in the provider bundle. Measured on case 03 and left off:
Flash saved five cents on the IaC author and took twice the requests.
- Steps 7 and 9 decided against on the numbers, recorded in the plans.
- Plans: the runs of cases 05 and 06, and the first proof of the lessons on
case 03 (no Revision, 22 minutes against 28, quality held).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Capture, distil, review, publish, retire (ADR-0004). Lesson candidates of
past Executions are grouped into what recurred; a lesson-curator role,
outside any Execution, proposes a lesson per group worth one; each proposal
is an issue file a person approves or rejects; an approved lesson is
written into the provider's lessons Skill, which a Specialist is given only
once it holds lessons for that Specialist's Deliverable. LESSONS_ENABLED
off runs without them, for an evaluation with and without.
The curator proposed six lessons from 21 Executions. The owner approved all
six on 2026-10-09 and they are published: five for the target architect,
one for the IaC author. None is proved by an evaluation yet.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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>
Increment 7 of .scratch/solution-architect-agent/spec.md.
- app/assembly.py: composition root building the engine from settings
and the provider bundle (roles, ADK runtime, MCP catalog, Terraform
tools, checkpointer, recorder).
- app/a2a: a2a-sdk 1.1 JSON-RPC server (v0.3 compatible) mapping tasks to
Executions; questions, Approvals and permissions pause as
input-required; Approvals accepted only as structured data; completed
tasks return the guide and code as artifacts; agent card derived from
the dependency graph.
- POST /generate runs a pre-approved Execution with the legacy keys.
- Specialist exceptions are relayed to the user; Orchestrator exceptions
fail the task. Engine accepts a caller-chosen execution id.
- Dockerfile installs checksum-verified Terraform and ships agents,
providers and skills; add mcp and a2a-sdk requirements.
- 17 new tests; full suite 206 passed.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Increment 6 of .scratch/solution-architect-agent/spec.md, test-first.
- app/tools/mcp.py: MCP client and catalog exposing only allowlisted,
readOnlyHint tools as framework-neutral ToolSpecs; unreachable servers
and failed calls become discovery gaps; ADC auth with quota project.
- app/tools/local.py: Mermaid structure check and Terraform fmt,
validate and plan in a scratch copy; apply is never constructed.
- Tool factory gives roles their named local tools and bundle MCP
servers; pillar advisors get general-tier documentation tools.
- providers/gcp.yaml: 42 allowlisted tools reviewed against live
tools/list of 12 Google Cloud MCP servers (snapshot in
providers/reviews/), excluding data-reading and secret-capable tools.
- scripts/list-mcp-tools.py, docs/operations/mcp-access.md (IAM deny
policy, service account roles), cloud-discovery and iac-validation
Skills, MCP and Terraform settings, pytest asyncio auto mode.
- 31 new tests; full suite 189 passed.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Increment 5 of .scratch/solution-architect-agent/spec.md, test-first.
- agents/*.md: provider-neutral role files for the Orchestrator, nine
Specialists and the pillar advisor, with a shared Specialist protocol.
- app/agents/roles.py: load and validate role files; Skills, MCP
servers and models come from the provider bundle.
- app/agents/adk_runtime.py: AgentRuntime on google-adk 2.9 with a
per-run LlmAgent, role-scoped SkillToolset (no run_skill_script),
step budgets, early stop on turn-ending tools, LiteLLM models.
- app/execution/pillars.py + toolkit.py: design advisor fans out to one
advisor per WAF pillar in parallel.
- Specialists receive every earlier-Phase Deliverable as input.
- Bundle gains role_skills, pillar_skills and -latest Gemini aliases;
pin google-adk[extensions]==2.9.0.
- 37 new tests; full suite 158 passed.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Increment 4 of .scratch/solution-architect-agent/spec.md, test-first.
- app/agents/runtime.py: framework-neutral AgentRuntime interface
(RoleSpec, AgentTask, ToolSpec, outcomes); fake_runtime.py replays
scripted tool calls through the real tools with step budgets.
- app/execution/graph.py: Orchestrator turn fans out to parallel
Specialist tasks (Send), pauses with interrupt() for questions,
Approvals and cloud-read permission, and finalizes or ends with
warnings. Only the Orchestrator turn writes the Ledger.
- app/execution/tools.py: Orchestrator tools, Specialist submit and
needs_input, and the cloud-read permission gate.
- app/execution/engine.py: ExecutionEngine.start/resume returning an
Interaction; the single interface for A2A, /generate and eval.
- Recorders (in-memory, DatabaseManager), configurable checkpointer
(memory, sqlite, postgres), engine settings, langgraph checkpoint
dependencies.
- 19 new tests; full suite 121 passed.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Increment 3 of .scratch/solution-architect-agent/spec.md, test-first.
- app/execution/deliverables.py: four Phases, nine Deliverables and
their Dependencies declared once, plus per-kind contracts (required
headings, attachments) checked by check_submission.
- app/execution/ledger.py: pure Ledger enforcing both acceptance
thresholds, Phase Approvals (including pre-approved mode and change
requests), Revision cascade with withdrawn Approvals, the revision
cap with escalation and user override, attempt numbers that reject
stale submissions, an ordered event log, and dict round-tripping.
- 37 new tests; full suite 102 passed.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Increment 2 of .scratch/solution-architect-agent/spec.md.
- Vendor google-cloud-solution-architecture and the six
google-cloud-waf-* Skills from google/skills@81a31a6, unmodified,
with LICENSE, SHA256SUMS and VENDOR.md; add
scripts/sync-vendored-skills.sh to re-sync at a pinned sha.
- app/agent_skills.py: discover Skills and validate SKILL.md
frontmatter against the Agent Skills specification.
- app/providers.py + providers/gcp.yaml: load and validate a Cloud
provider bundle (Skills, output template, per-role models, tool
tiers, remote MCP servers). MCP allowlists stay empty until the
read-only review in increment 6.
- Settings CLOUD_PROVIDER and MCP_ENABLE_PREVIEW.
- 35 new tests; full suite 65 passed.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
30 passed on the current suite; notes resolved dependency versions,
SQLite fallback, and test side effects (execution dirs, tracked pyc).
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Record the direction and build plan for replacing the upstream
google-cloud-solution-architecture skill with a portable agent.
- ADR-0002: Agent Skills are the portable unit of behaviour, loaded by
the framework's native skill runtime; discovery and grounding use
each Cloud provider's hosted remote MCP servers.
- ADR-0003: LangGraph holds Execution state, checkpoints and
interrupts; a ReAct Orchestrator and Specialists run as ADK
LlmAgents with SkillToolset. Supersedes ADR-0001.
- CONTEXT.md: domain glossary (Execution, Phase, Approval, Revision,
Orchestrator, Specialist, Deliverable, Dependency, Cloud provider).
- .scratch/solution-architect-agent/spec.md: build spec with the
dependency graph, Revision rules, tool tiers, MCP allowlists, A2A
interaction, tests and nine build increments.
- .scratch/phase-pipeline/spec.md: superseded; kept as decision log.
- CLAUDE.md and docs/agents/: agent skill configuration (local
markdown issue tracker, triage labels, domain docs).
- README.md: direction note; flags current ADK classes as stubs.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>