- 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>
3.2 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 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.
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.