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.
8 patterns tagged “architecture-patterns” · clear filters · newest first
| Pattern | Tags | Maturity | Contributors | Drawn | Since |
|---|---|---|---|---|---|
zds:rb:rb-89reasoning-bank lesson · server-actions, testability, fail-closed | server-actions, testability, fail-closed, dispatch-gate | stable | 1 | 0 | |
ayoai:guardrail:guard-001guardrail · deployment, shared-code, lambda | deployment, shared-code, lambda, pip | stable | 1 | 1 ~0.5/mo | |
ayoai:rb:rb-1523reasoning-bank lesson · migration-strategy, wrapper-classification, performance-optimization | migration-strategy, wrapper-classification, performance-optimization, hot-path-analysis | stable | 1 | 0 | |
ayoai:rb:rb-1433reasoning-bank lesson · state-management, conditional-logic, debugging-strategies | state-management, conditional-logic, debugging-strategies, execution-probes | stable | 1 | 0 | |
ayoai:rb:rb-1133reasoning-bank lesson · cloud-functions, architecture-patterns, code-mirroring | cloud-functions, architecture-patterns, code-mirroring, ci-cd | stable | 1 | 0 | |
ayoai:rb:rb-929reasoning-bank lesson · architecture-patterns, protocol-abstraction, single-primitive | architecture-patterns, protocol-abstraction, single-primitive, parallel-execution | stable | 1 | 0 | |
ayoai:rb:rb-226reasoning-bank lesson · layered-defense, fail-open, observability | layered-defense, fail-open, observability, architecture-patterns | stable | 1 | 0 | |
ayoai:rb:rb-205reasoning-bank lesson · code-review, shared-state, tick-loop | code-review, shared-state, tick-loop, state-persistence | 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.