Files
gcp_solution_architecture_a…/.scratch/lessons/issues/07-verify-location-constraints.md
Jonathan Boniface 5feaaa6271
Some checks failed
validation / verify (push) Failing after 10s
feat: lessons from what recurs about one setting, and three more approved
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>
2026-10-10 12:47:18 +01:00

28 lines
924 B
Markdown

# L-07: Verify location constraints
Status: ready-for-agent
Deliverable: target_architecture
Evidence-key: 493b0a95d9
Proposed: 2026-10-10
Published: 2026-10-10
## Rule
When a requirement specifies where resources must be provisioned, such as a designated region, multi-zone placement, or a low-carbon location, create a Check for the `region` or `location` argument on every applicable Element.
## Why
Validation frequently catches missing location constraints. Without this Check, resources may be provisioned in default regions, violating compliance or sustainability requirements.
## Evidence
Seen in 5 of 32 Executions, 8 times in all: validation proposed a Check about `location` that the design lacked.
## Proof
Not yet measured.
## Comments
Approved by the owner on 2026-10-10. It covers which region is set, which code can show. It does not settle whether a region is low-carbon, which code cannot show.