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>
774 B
774 B
L-09: Backend Service capabilities
Status: ready-for-agent Deliverable: target_architecture Evidence-key: 1cacec9a09 Proposed: 2026-10-10 Published: 2026-10-10
Rule
When writing Checks for a google_compute_backend_service, do not verify IAM roles inside the backend service or require health checks when it is configured with a Serverless NEG.
Why
Roles are verified via IAM bindings outside the backend service, and Serverless NEGs do not support health checks. Invalid Checks cause the design to be rejected during validation.
Evidence
Seen in 3 of 32 Executions, 3 times in all: a Check about google_compute_backend_service asked for something that resource cannot do.
Proof
Not yet measured.
Comments
Approved by the owner on 2026-10-10.