feat: prove the lessons, check overlays in evaluation, and settle the cost steps
Some checks failed
validation / verify (push) Failing after 13s
Some checks failed
validation / verify (push) Failing after 13s
- Schema review: a dotted path is judged only when it starts at a name the resource type has, so a database flag or a service name is no longer read as a missing setting. Lesson L-04, which worked around that, is retired. - Skill routing: in a Change request the question says what changed. - Evaluation: a case may list code_standards the infrastructure code must meet; case 06 checks its overlay's regions, naming and labels. - Model tiers (iteration 5 step 6): a lighter model for a role's first attempt, named in the provider bundle. Measured on case 03 and left off: Flash saved five cents on the IaC author and took twice the requests. - Steps 7 and 9 decided against on the numbers, recorded in the plans. - Plans: the runs of cases 05 and 06, and the first proof of the lessons on case 03 (no Revision, 22 minutes against 28, quality held). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -26,14 +26,6 @@ Published 2026-10-09, from lesson proposal 02.
|
||||
|
||||
Published 2026-10-09, from lesson proposal 03.
|
||||
|
||||
## L-04: Avoid Using Values as Setting Names
|
||||
|
||||
**Rule.** When writing a Check for a configuration block that takes a name and value, explicitly state the block's argument name instead of writing the expected value as if it were the setting itself.
|
||||
|
||||
**Why.** Automated reviews may mistake specific expected values for invalid setting names, causing warnings and submission delays.
|
||||
|
||||
Published 2026-10-09, from lesson proposal 04.
|
||||
|
||||
## 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.
|
||||
|
||||
Reference in New Issue
Block a user