- 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>
1.1 KiB
L-05: Include Required Arguments in Alert Policies
Status: ready-for-agent Deliverable: deployment_guidance Evidence-key: 2d4ff48141 Proposed: 2026-10-09 Published: 2026-10-09
Rule
Always verify and include all required arguments (such as time window definitions) when configuring nested blocks in monitoring alert policies.
Why
Missing required arguments in nested blocks will cause Terraform validation to fail, preventing submission.
Evidence
Seen in 2 of 21 Executions, 2 times in all: terraform_validate refused: terraform validate failed: Error: Missing required argument on main.tf line …, in resource … …: …: condition_m.
Proof
Evaluation without lessons: 20261009T195603Z; with: 20261009T195607Z.
| Case | Score | Revisions | Minutes | Tokens (M) |
|---|---|---|---|---|
| case-03-internal-web-app | 1.00 → 1.00 | 1 → 0 | 28 → 22 | 3.00 → 2.32 |
Quality held and revisions, seconds, tokens fell: kept.
This compares every published lesson together, on one run each way. Runs of the same case vary, so one pair suggests a direction and does not settle it.
Comments
Approved by the owner on 2026-10-09.