Every Execution now begins by agreeing the scope, before requirements.
- A new Phase and Deliverable, produced by a scope analyst with two tools:
scope_read shows what is settled and what is not; scope_set records fields
with where each value came from (the request, the customer's answer, or an
assumption with its reason). Code checks each value against the catalogue.
- With someone present the analyst asks for what is missing; with nobody
present it assumes it, visibly. With no spec it drafts one from the request.
A value the customer stated in the file is changed only by their own answer.
- A submission cannot leave an essential field unknown. Code writes the
completed spec, the data every later Specialist reads, and the information
register, from what was recorded.
- The spec's status follows the Execution: under review, approved, then
locked as a Baseline. A Change request starts from the delivered scope.
- The requirements analyst derives from the agreed scope and no longer asks
for what it settles.
About 80 tests assumed requirements came first; tests/scoped.py runs scoping
ahead of a test's own script, and tests about order and counts are updated.
Not run with real models.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A reviewer role reads the requirements and recommendations against the Checks
when the Target architecture is first submitted. Three runs of case 03: it did
not stop the validator sending the design back, and the designs it reviewed
ended with 87 and 93 Checks against 52, so they cost more. It stays behind
DESIGN_COVERAGE_REVIEW, off (iteration 6 step 13).
Also: the schema review no longer reads `true` or `false` in backticks as a
setting name.
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>
After case 02 (completed at 100%, but with two Revisions of the Target
architecture for gaps validation found one pass at a time):
- A Deliverable stands while what it was written from is unchanged. The
architecture description is written from the Elements and Relationships,
so a Revision that only adds or rewords Checks no longer runs the describer.
- Non-functional requirements and recommendations list their conditions,
one entry per separate thing that must be true; submission requires them.
- A coverage review at submission (JEV_COVERAGE_REVIEW, off by default):
for each condition, Jev chooses which Check verifies it, or none. Asked as
one broad yes-or-no per requirement it could not tell a complete design
from one with known gaps; asked as a choice per condition it raised all
four known gaps of case 02 and nothing on the complete graph. An opt-in
live test (LIVE_JEV=1) repeats that.
- The validator is told to report every gap in its first pass.
Plans record the case 02 run and both forms of the review with figures.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Start-up
- Export the env file's variables for other libraries (the Cloud provider's
client) into the process environment; the app's own settings and secrets
are never exported, and a value already in the environment wins.
- Use GOOGLE_GENAI_USE_ENTERPRISE in place of the deprecated
GOOGLE_GENAI_USE_VERTEXAI.
Target architect
- Look each distinct resource type up once instead of once per setting: in
the run of 2026-10-07 it made 39 lookups for 8 types and exhausted its
budget. terraform_schema's find takes several names; budget 30 to 45.
- A cut-off schema outline says so.
Removed, as leftovers of the original pipeline that nothing read
- terraform/ (no longer passed terraform validate), scripts/validate.sh,
tests/test_package.py and the CI steps that ran on them.
- The sample outputs under docs/ and requirements.yaml.
- CI now pins Terraform 1.14.3, as the container image does.
Plans record the case 01 run: completed at 100% in 18 minutes with no
Revision, against 60 minutes and warnings before.
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>