Some checks failed
validation / verify (push) Failing after 10s
Evidence was grouped only by the kind of problem, and a group gets one lesson, so what kept recurring inside "validation proposed a Check" could not be seen. A proposed or unimplementable Check is now also counted under each provider setting or resource type it names; a subject seen in two or more Executions is its own group and reaches the curator past triage. Over 32 Executions that gave five proposals. The owner approved three, now published: L-07 location Checks, L-08 Cloud SQL backup encryption, L-09 backend service capabilities. L-10 is held for more evidence and L-11 rejected. Also: retiring a lesson marks its proposal, so publish no longer brings a retired lesson back. L-04 had returned to the Skill that way. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
31 lines
979 B
Markdown
31 lines
979 B
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
|
|
Retired: 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.
|
|
|
|
- 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.
|