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>
Plans
One directory per iteration of this agent. Each holds the plan for that iteration and, for finished steps, the record of what was built. Read the row for the iteration you are working in, then its MAP.md.
Iterations
| # | Directory | Status | What it is |
|---|---|---|---|
| 1 | wf-decompose-65ea49fc2d04/ |
complete, superseded | The decomposer's scaffold: a linear four-phase pipeline of template functions. Its code was deleted in iteration 3 and survives only in git history. Generated by the platform decomposer; leave its files as written. |
| 2 | iter-02-solution-architect-agent/ |
complete; step 9 was done in iteration 3 | The rebuild as a hierarchical ReAct agent: Orchestrator, one Specialist per Deliverable, Skills, provider bundle, A2A. |
| 3 | iter-03-kab-layout/ |
complete (commit 7ee49ab) |
The container starts the new engine, the engine moved into the KAB workflow-agent folder layout, and the original pipeline was deleted. |
| 4 | iter-04-learning-and-skills/ |
steps 1–8, 11, 13 and 15–27 built; cases 01, 02 and 03 completed at 100% on them on 2026-10-07 and 08; ADR-0004 accepted 2026-10-08 (step 9); the lessons loop is built and its first six lessons are approved and published, with a first proof on case 03: no Revision, 22 minutes against 28 (step 10); overlay Skills built and run in case 06 (step 12); 14 deferred until a second Cloud provider | The enhancement backlog from the 2026-10-06 review: cheap fixes, the learning loop through Skills, overlay Skills, provider neutrality. Steps 17–20 are the speed-ups from the 2026-10-07 run: a working copy for files and the graph, a provider schema lookup, routing a Check the code cannot meet, and a model timeout per role. |
| 5 | iter-05-jev-decisions/ |
the router, intake, the reviews, pillar selection, Skill routing, the guardrail, meaning-aware change summaries and an assessment of every Execution are built (steps 2–5, 8, 10–12, 14, 15, 19), the newest ran in cases 05 and 06 on 2026-10-09; a lighter model for a first attempt was built, measured and left off (6); context selection and compaction were decided against on the numbers (7, 9); the cloud-read guard and readings as a node are planned (13, 18) | Jev (a hosted decision model) for the agent's closed decisions: checks, routing, context selection. |
| 6 | iter-06-target-architecture-graph/ |
complete: all four cases pass with real models, each run twice on 2026-10-08; thresholds set | The Target architecture as one explicit graph of Elements, Relationships and Checks, established before infrastructure code, with validation as a verdict per Check. |
| 7 | iter-07-change-requests/ |
complete (2026-10-09): the change case ran with real models and passed | A user restates a request to say how requirements changed; a new Execution starts from a Baseline Execution of the same Customer case and delivers the updated architecture with what changed. |
| 8 | iter-08-terraform-modules/ |
steps 1–5 built on 2026-10-09; no case has run with them; steps 6 and 7 wait on Azure and AWS provider bundles | Infrastructure code is plain resources by default. An Execution may opt into published Terraform modules: only from registry namespaces the provider bundle lists, at one exact version, with a lookup of what a module accepts and a Skill of four Google modules tested against the pinned provider. |
Numbers record when an iteration was planned, not the order to build in. Build iteration 6 before the remaining steps of iteration 4 (10 to 14) and before iteration 5: it changes the Deliverables, Phases and validation format they build on. Its MAP.md lists the effect on each of their steps.
Two designs sit between iterations 1 and 2 and have no plan directory. Commit a24a44e wrapped the pipeline in a compatibility layer that imitated Google ADK without using it (deleted in iteration 3). .scratch/phase-pipeline/spec.md then designed a code-sequenced Phase pipeline; ADR-0002 reopened it before any of it was built, and its decision log (D1 to D46) explains how iteration 2's design was reached.
Files in an iteration
MAP.md: the intent, each step's status, the dependency graph between steps, and the sources of truth to read.DETAIL.md: per step, the capability, why it exists (with evidence), where the change lands, and the acceptance criteria.steps/step-N.md: written when step N is finished. What was built, what differed from the plan, and how it was verified. A step with no file is not done.
Steps are numbered from 1 in iterations 2 onward. Iteration 1 numbers from 0.
Working in an iteration
- Read
MAP.md, then theDETAIL.mdentry for your step and every step it depends on. - Read the sources of truth
MAP.mdnames. Plans point at specs and ADRs; they repeat only what those lack. - Build the step until every acceptance criterion in its
DETAIL.mdentry holds and.venv/bin/python -m pytest -q,.venv/bin/ruff check .and.venv/bin/mypy .all pass. - Write
steps/step-N.mdand set the step's status inMAP.mdtocomplete. When the last step closes, update the iteration's row above.
A new iteration gets the next number, a directory iter-NN-<slug>/, and a row above.
Module paths changed in iteration 3
Iteration 2's spec and ADR text name the modules by their old paths. The code is here now:
| Old path | Current path |
|---|---|
app/execution/deliverables.py |
app/workflows/deliverables.py |
app/execution/graph.py |
app/nodes/execution_nodes.py (nodes) and app/workflows/execution_graph.py (wiring) |
app/execution/engine.py, app/assembly.py |
app/agent.py |
app/execution/state.py |
app/states/execution_state.py |
app/execution/ledger.py |
app/states/ledger.py |
app/execution/tools.py, toolkit.py, pillars.py |
app/tools/execution.py, app/tools/toolkit.py, app/tools/pillars.py |
app/execution/recorder.py, checkpointing.py, presentation.py |
app/recorder.py, app/checkpointing.py, app/presentation.py |
app/agents/{runtime,adk_runtime,fake_runtime,roles}.py |
app/adk/ (same file names) |
app/agent_skills.py |
app/skills/agent_skills.py |
app/a2a/server.py, executor.py, card.py |
app/main.py, app/a2a_server.py, app/card.py |
the pre-rebuild app/agent.py, app/card.py, app/adk/, app/nodes/, app/workflows/, app/skills/, app/states/ deleted; in git history up to e94b249 |
|
tests/test_{adk_architecture,agent_api,graph_workflow,mcp_developer_knowledge,skill_loader}.py |
deleted |
eval/{metrics,optimizer,eval_harness,test_eval_harness}.py, eval/datasets/benchmark_cases.json |
deleted |
app/adk/, app/nodes/, app/workflows/, app/skills/ and app/states/ therefore mean different code before and after iteration 3. In text written before 2026-10-06, those names refer to the deleted original pipeline.