feat: lessons from what recurs about one setting, and three more approved
Some checks failed
validation / verify (push) Failing after 10s
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>
This commit is contained in:
26
.scratch/lessons/issues/10-pub-sub-persistence-regions.md
Normal file
26
.scratch/lessons/issues/10-pub-sub-persistence-regions.md
Normal file
@@ -0,0 +1,26 @@
|
||||
# L-10: Pub/Sub persistence regions
|
||||
|
||||
Status: needs-info
|
||||
Deliverable: target_architecture
|
||||
Evidence-key: ba78caba9a
|
||||
Proposed: 2026-10-10
|
||||
|
||||
## Rule
|
||||
|
||||
When a requirement dictates that a messaging queue or topic must replicate across zones or stay within a specific region, create a Check for the `message_storage_policy.allowed_persistence_regions` argument on the topic Element.
|
||||
|
||||
## Why
|
||||
|
||||
Without this Check, topics might use default storage policies that violate geographical or high-availability requirements.
|
||||
|
||||
## Evidence
|
||||
|
||||
Seen in 2 of 32 Executions, 4 times in all: validation proposed a Check about `allowed_persistence_regions` that the design lacked.
|
||||
|
||||
## Proof
|
||||
|
||||
Not yet measured.
|
||||
|
||||
## Comments
|
||||
|
||||
Held by the owner on 2026-10-10, on the agent's view: seen in 2 of 32 Executions, and L-07 partly covers it. To be looked at again if it recurs.
|
||||
Reference in New Issue
Block a user