Some checks failed
validation / verify (push) Failing after 10s
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>
1.2 KiB
1.2 KiB
name, description, metadata
| name | description | metadata | ||
|---|---|---|---|---|
| google-cloud-lessons | Rules learned from earlier solution-architecture work on Google Cloud, one set per Deliverable. Each was proposed from problems that recurred across Executions, approved by a person, and kept only while evaluation shows it helps. Use before drafting a Deliverable, to read the lessons for that Deliverable and follow them. |
|
Lessons
Each reference below holds the lessons for one Deliverable. Read the one for the Deliverable you are producing, with load_skill_resource, before you draft, and follow every rule in it that applies. A rule here takes precedence over a general habit; your role's instructions and the contract submit_deliverable checks take precedence over a rule here.
| Deliverable | Reference | Lessons |
|---|---|---|
| deployment guidance | references/deployment_guidance.md |
1 |
| target architecture | references/target_architecture.md |
7 |
This Skill is written by the lessons loop (app/learning/), from proposals a person approved. Do not edit it by hand: change the proposal and publish again.