Files
gcp_solution_architecture_a…/skills/google-cloud-lessons/references/target_architecture.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

3.1 KiB

Lessons: target architecture

Rules learned from earlier work. Follow every one that applies.

L-01: Create Specific Checks for All Constraints

Rule. Create specific Checks for every explicit constraint, metric, or capability mentioned in a requirement, rather than relying on a single broad Check.

Why. If detailed constraints are missed, the validation phase will reject the design for incomplete coverage, forcing a revision.

Published 2026-10-10, from lesson proposal 01.

L-02: Assign Checks to Every Element

Rule. Give every Element at least one Check before you submit.

Why. The submission tool will reject the architecture if any Element lacks a Check, wasting an attempt.

Published 2026-10-10, from lesson proposal 02.

L-03: Verify Resource Arguments for Checks

Rule. Verify that the specific resource type used for an Element actually supports the configuration argument you specify in a Check. Remember that access policies and certain configurations often require entirely separate resources.

Why. If a Check specifies an argument that does not exist on the resource, it cannot be implemented, forcing an architectural revision.

Published 2026-10-10, from lesson proposal 03.

L-06: Do Not Mark Requirements as Not Applicable

Rule. Do not list Requirements in the not applicable field, as this field is strictly for Design Recommendations. Ensure every Requirement has at least one Check.

Why. The submission tool will reject the deliverable if a Requirement lacks a Check or is incorrectly marked as not applicable.

Published 2026-10-10, from lesson proposal 06.

L-07: Verify location constraints

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.

Published 2026-10-10, from lesson proposal 07.

L-08: Cloud SQL backup encryption

Rule. When writing a Check for CMEK encryption on a google_sql_database_instance, do not require an encryption_key_name argument for backup storage, as the instance-level encryption_key_name automatically encrypts backups as well.

Why. The database instance resource does not have a separate encryption key argument for backups. Asking for one causes validation to reject the Check as un-implementable.

Published 2026-10-10, from lesson proposal 08.

L-09: Backend Service capabilities

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.

Published 2026-10-10, from lesson proposal 09.