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>
Infrastructure code is plain resources by default. An Execution may opt in
with terraform_modules; the deployment default is TERRAFORM_MODULES, off.
- A module is accepted only from the registry namespaces the provider bundle
lists (terraform-google-modules), at one exact version. Any other source is
refused before Terraform runs; until now nothing stopped generated code
naming any source for terraform init to download.
- terraform_module looks up a module's inputs, outputs and submodules from
the registry and says when it cannot be used with the pinned provider.
- skills/google-cloud-iac-modules: when a module fits, and four modules with
examples a test validates against hashicorp/google 8.6.0.
- Opted in, the IaC author and validator get the Skill and the lookup. Not
opted in, they get neither and a module block is refused in code.
- A Change request follows its Baseline. execution.json records the choice.
- case-07 runs case 03's request with modules opted into.
Azure (aztfm) and AWS (terraform-aws-modules) sources are recorded in the
plan for when those Cloud providers are added. No case has run with this.
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>
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 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>