Files
gcp_solution_architecture_a…/.scratch/lessons/issues/05-include-required-arguments-in-alert-policies.md
Jonathan Boniface a7bc5310f3 feat: the lessons loop, and six lessons approved and published
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>
2026-10-09 15:19:32 +01:00

28 lines
736 B
Markdown

# 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
Not yet measured.
## Comments
Approved by the owner on 2026-10-09.