feat: lesson L-10 approved and published (Pub/Sub persistence regions)

Held for thin evidence, then its subject caused a Revision again in case 06.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-10-10 16:01:11 +01:00
parent 7ee7054523
commit f9cc34817b
3 changed files with 13 additions and 2 deletions

View File

@@ -18,7 +18,7 @@ Each reference below holds the lessons for one Deliverable. Read the one for the
| Deliverable | Reference | Lessons |
| --- | --- | --- |
| deployment guidance | `references/deployment_guidance.md` | 1 |
| target architecture | `references/target_architecture.md` | 7 |
| target architecture | `references/target_architecture.md` | 8 |
<!-- lessons:end -->
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.

View File

@@ -57,3 +57,11 @@ Published 2026-10-10, from lesson proposal 08.
**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.
## L-10: Pub/Sub persistence regions
**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.
Published 2026-10-10, from lesson proposal 10.