- 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>