A pillar's checklist item the request gives no information about was marked
"not addressed", which reads as a fault in the design. It is missing
information. The checklist review gains a fourth outcome, to confirm with the
customer, which must carry the question to ask. The questions are written
into the design recommendations and the guide, and to customer-questions.md;
the evaluation's judged check counts such an item as accounted for.
Records the owner's decisions of 2026-10-10 and the vendor's answers on Jev's
retention, training, context and rate limits (iteration 5 step 1), and the
owner's labels, which showed the judged question was wrong, not the judges.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Case 06 reached its Revision limit because the validator failed a Check that
a role is granted, for the identity also holding other roles, and the IaC
author could only answer by recording the Check as unimplementable. The
validator is told what its own words require; the author is told to dispute
such a verdict and change nothing.
The evaluation's naming standard for case 06 accepted only a variable inside
each name; it now accepts names built from a local as well.
Records the reruns: case 04 passed at 12 of 12, case 06 ended with warnings.
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>
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>
Iteration 4:
- Overlay Skills (step 12): an Execution names an organisation's standards
Skill from the folders the deployment configures; recorded with its version.
An example standards Skill and an evaluation case that uses it.
- Lessons (step 10): a prove command that compares a run with lessons against
one without, and triage of evidence an existing lesson already covers.
Iteration 5:
- Step 8: the references of a Specialist's Skills its task needs are named in
its context as read_first.
- Step 14: a remote MCP server's reply that instructs the agent is withheld;
the user's own text is flagged as a risk and nothing more.
- Step 15: in a Change request, items only reworded are listed apart from
real changes.
- Step 19: each Execution's design recommendations are judged when it ends and
the scores kept in its record. The evaluation takes its rubric from the same
place.
Each question was calibrated against live Jev; none has run in a case. Steps
6, 7, 9, 13 and 18 stay planned, with the reasons in the plan map.
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>
The change-case check asked for a changed Check whose source is the changed
requirement. A functional requirement is carried by the components that
serve it, so it is reached through a Check on an Element realising one.
Plans record the first Change request with real models: a retention change
made in 18 minutes for a third of its Baseline's tokens, touching seven
Checks on one Element and nothing else, and the regression runs of cases
02, 03 and 04, all at 100%. Iteration 7 is complete.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A caller restates a request to say how requirements have changed, naming a
completed Execution of the same Customer case as the Baseline.
- app/baseline.py reads a Baseline from its files and refuses one that
does not exist, did not complete or belongs to another case, before
anything runs or is recorded. A Baseline is never modified.
- Requirements carry a change (unchanged, added, changed, removed) and a
reason. Submission is refused when a Baseline requirement disappears, an
id is reused, or an unchanged requirement's text differs. A removed
requirement stays on record and asks nothing downstream.
- Each Specialist starts from its delivered version; the graph and the code
are its working copy, and the description is carried over when the
design's shape is the same.
- app/workflows/changes.py compares versions by id and traces what each
changed requirement reaches; anything else that changed is listed as
unrequested. Approvals show the change for their Phase, and changes.json
is written with the full Deliverables.
- Intake no longer starts a message read as a change: it names the
Execution to give as the Baseline.
- A fifth evaluation case runs a request and then a change to it, with
four checks that the change is recorded, reaches Checks, stays contained
and costs less than its Baseline.
Tested with scripted agents only; no Change request has run with real
models.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Case 04 (interactive)
- A scripted answer may name who it is for, so facts written for
requirements discovery are not given to a Specialist confirming a draft.
- A reply that restates what the agreed requirements already say is read
as an answer, not a request for changes.
- With a user present, a first submission is refused until the user has
been shown a draft of that Deliverable (CONFIRM_DRAFTS).
Routing and reviews
- Intake: a message that starts something is read first. A question is
answered and starts nothing; a change to delivered work starts as a new
request with a note, until Change requests are built.
- Requirements and recommendations list what infrastructure code can show
(conditions) apart from what it cannot (outside_code); the latter needs
no Check and validation proposes nothing for it.
- A requirements review, "names no products", behind its own switch (off).
- Each pillar advisor reviews its pillar's checklist; the engine writes the
reviews into the design recommendations. The judged checklist check went
from 9-45% a pillar to 100% in one run of case 04.
Evaluation
- Per-case thresholds for Revisions, seconds and tokens, set from every
completed run on this build.
- A progress file after every agent run, so an interrupted run keeps its
time and tokens.
- eval/calibrate_judge.py with a 32-question set awaiting a person's
labels. Unlabelled: Jev stable at 1.00, Gemini 0.92, agreeing on 0.91.
Smaller
- An Execution that ends with warnings writes its Deliverables, with the
warnings and each status in the manifest.
- CI installs the application's dependencies before linting and testing.
- A load-balancer pattern in the IaC patterns Skill.
Plans record nine runs of 2026-10-08. Iteration 6 is complete.
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>
These 30 .pyc files were committed before .gitignore covered them and
changed on every test run. Files remain on disk; .gitignore already
excludes __pycache__/ and *.pyc.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>