Rules

• Do not commit bespoke verifier scripts Retired verifier basenames are prohibited everywhere. Other executable-script basenames beginning with verify require objective source, test, script, bin, or component ownership, including at the repository root. Operational placement remains prohibited except for conventional source inside an objectively owned tool or harness. bespoke-iac-verifiers error
• Do not commit example tfvars files Tracked filenames ending in .tfvars.example, .tfvars.sample, or .tfvars.template are prohibited. terraform-examples error
• Do not commit native Terraform test files Tracked paths ending in .tftest.hcl or .tftest.json are prohibited, case-insensitively. terraform-test-files error
• Keep script tests out of operational trees Executable script test/spec artifacts are prohibited in operational trees. Repository Standards owns this path boundary; semantic workflow analysis belongs in Code Standards. operational-script-tests warning
• Reject hand-maintained configuration examples Tracked backend.conf and env example, sample, template, or schema basenames are prohibited, case-insensitively. schema-derived-config-examples warning
• Keep Markdown in durable owned locations Tracked Markdown must have a durable documentation or tool-contract role. documentation-placement error