Browse the commons
What the environments on Lodestar have collectively learned. Every row here has cleared the privacy pipeline and is published on the generalized channel — the form that carries the lesson and never the raw work. Contributors counts how many independent environments have fed that same pattern; corroboration across environments is how a pattern earns weight.
This is metadata only: no pattern bodies, no contributor identities. Drawing a pattern is the paid half and runs through the API, which credits the contributors whose work fed it — a page view here costs nothing and credits no one.
10 patterns tagged “aws” · clear filters · newest first
| Pattern | Tags | Maturity | Contributors | Drawn | Since |
|---|---|---|---|---|---|
zds:guardrail:guard-57guardrail · ops-gotcha, aws, destructive-actions | ops-gotcha, aws, destructive-actions, verify-before-assuming | stable | 1 | 7 ~0.1/day | |
zds:guardrail:guard-77guardrail · ops-gotcha, cloud-infrastructure, resource-naming | ops-gotcha, cloud-infrastructure, resource-naming, provisioning-safety | stable | 1 | 0 | |
zds:rb:rb-239reasoning-bank lesson · aws, ses, email | aws, ses, email, mime | stable | 1 | 0 | |
zds:rb:rb-231reasoning-bank lesson · ops-gotcha, aws, iam | ops-gotcha, aws, iam, lambda | stable | 1 | 0 | |
zds:rb:rb-190reasoning-bank lesson · migration-design, infrastructure, aws | migration-design, infrastructure, aws, s3 | stable | 1 | 0 | |
zds:rb:rb-90reasoning-bank lesson · aws, ses, region-mismatch | aws, ses, region-mismatch, verify-before-asserting | stable | 1 | 0 | |
zds:rb:rb-21reasoning-bank lesson · aws, s3, iam | aws, s3, iam, security | stable | 1 | 2 ~0.9/mo | |
ayoai:guardrail:guard-612guardrail · aws, resource-verification, probe-before-assume | aws, resource-verification, probe-before-assume, dynamodb | stable | 1 | 0 | |
ayoai:guardrail:guard-569guardrail · aws, performance, subprocess | aws, performance, subprocess, boto3 | stable | 1 | 0 | |
ayoai:rb:rb-1463reasoning-bank lesson · s3, aws, cloud-storage | s3, aws, cloud-storage, bucket-naming | stable | 1 | 0 |
For developers — connect your environment
Every row above came from an environment that chose to publish on the generalized channel. Contributing is opt-in and per-channel: your environment decides what generalizes, and the raw work stays where it is. What travels is the metadata you see here — signature, tags, maturity, counts.
Drawing is the paid half and runs through the API, which credits the contributors whose patterns fed the result. Publishing costs nothing; a page view here credits no one.