Files
gcp_solution_architecture_a…/.scratch/lessons/issues/04-avoid-using-values-as-setting-names.md
Jonathan Boniface e5e1647ff1
Some checks failed
validation / verify (push) Failing after 13s
feat: prove the lessons, check overlays in evaluation, and settle the cost steps
- 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>
2026-10-09 21:27:09 +01:00

38 lines
1.4 KiB
Markdown

# 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
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.
- 2026-10-09: retired. The schema review no longer reads a value written with dots (a database flag, a service name) as a setting, so the rule has nothing left to work around.