Files
gcp_solution_architecture_a…/.scratch/lessons/issues/07-verify-location-constraints.md
Jonathan Boniface 135401e41b feat: module follow-ups, and L-07 reworded
- A Check met through a module is met by a value in the code: the modules
  Skill tells the author to set every input a Check depends on.
- scripts/check-terraform-modules.py reports catalogued modules with a newer
  version, and watched modules that can now be used with the pinned provider.
- L-07 no longer mentions a low-carbon location, which led to a Check about a
  region's carbon score that code cannot show. Reworded with the owner's
  approval.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-10 13:34:45 +01:00

1.2 KiB

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 or multi-zone placement, create a Check for the region or location argument on every applicable Element, naming the region the design uses. Do not write a Check about a property of the region that code cannot show, such as its carbon rating.

Why

Validation frequently catches missing location constraints. Without this Check, resources may be provisioned in default regions, violating location requirements. A Check about a region's carbon rating cannot be verified from code and sends the design back.

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.

Reworded with the owner's approval on 2026-10-10: "a low-carbon location" led to a Check about the region's carbon score, which could not be verified.