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>
- 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>
From the case 02 run cancelled at 66 minutes on 2026-10-07:
- The validator records verdicts a few Checks at a time (verdict_put) and
they are attached on submission. It timed out five times writing them in
one reply. Verdicts on the same code survive a run cut short; verdicts on
changed code are dropped. Its model timeout is 300 s.
- A schema review at submission, in code: every setting a Check names is
looked up on its Element's resource type, and an unknown resource type is
reported. Two Revisions in that run were for Checks no code could meet.
On the two designs that passed validation it raises 2 of 96 Checks, both
one metric name used as a value, so it is returned once and never blocks.
- Reviews run together; the Jev coverage review stays off.
Plans record both steps and the cancelled run.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>