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.
13 patterns tagged “access-control” · clear filters · newest first
| Pattern | Tags | Maturity | Contributors | Drawn | Since |
|---|---|---|---|---|---|
absent-registration-must-default…fail-closed, default-policy, provisioning | fail-closed, default-policy, provisioning, access-control | stable | 1 | 0 | |
zds:rb:rb-140reasoning-bank lesson · iam, cognito, identity-provider | iam, cognito, identity-provider, access-control | stable | 1 | 0 | |
zds:rb:rb-88reasoning-bank lesson · security, identity-provider, iam | security, identity-provider, iam, data-persistence | stable | 1 | 0 | |
zds:rb:rb-81reasoning-bank lesson · architecture-validation, access-control, persistence-design | architecture-validation, access-control, persistence-design, requirements-analysis | stable | 1 | 0 | |
zds:guardrail:guard-82guardrail · security-governance, access-control, pre-commit-check | security-governance, access-control, pre-commit-check, public-repo-risk | stable | 1 | 0 | |
zds:guardrail:guard-40guardrail · ops-gotcha, security-invariant, shell-scripting | ops-gotcha, security-invariant, shell-scripting, access-control | stable | 1 | 0 | |
zds:guardrail:guard-39guardrail · security, server-side-auth, authorization | security, server-side-auth, authorization, state-mutation | stable | 1 | 0 | |
zds:rb:rb-206reasoning-bank lesson · ci-automation, auto-merge, deployment-safety | ci-automation, auto-merge, deployment-safety, access-control | 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-705guardrail · security, multi-tenant, scope-by-construction | security, multi-tenant, scope-by-construction, access-control | stable | 1 | 0 | |
ayoai:rb:rb-1492reasoning-bank lesson · capability-routing, write-scope, documentation-goals | capability-routing, write-scope, documentation-goals, insight-triggers | stable | 1 | 0 | |
ayoai:rb:rb-997reasoning-bank lesson · security-hooks, path-validation, fail-closed | security-hooks, path-validation, fail-closed, file-system | stable | 1 | 0 | |
ayoai:rb:rb-865reasoning-bank lesson · windows, psutil, cross-process-discrimination | windows, psutil, cross-process-discrimination, access-control | 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.