Files
gcp_solution_architecture_a…/.scratch/lessons/issues/04-avoid-using-values-as-setting-names.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

782 B

L-04: Avoid Using Values as Setting Names

Status: ready-for-agent Deliverable: target_architecture Evidence-key: 22ff1f5fed Proposed: 2026-10-09 Published: 2026-10-09

Rule

When writing a Check for a configuration block that takes a name and value, explicitly state the block's argument name instead of writing the expected value as if it were the setting itself.

Why

Automated reviews may mistake specific expected values for invalid setting names, causing warnings and submission delays.

Evidence

Seen in 2 of 21 Executions, 4 times in all: submit_deliverable refused: Not submitted. A review found: Check …: google_sql_database_instance has no setting named cloudsql.iam_authent.

Proof

Not yet measured.

Comments

Approved by the owner on 2026-10-09.