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.
4 patterns tagged “exit-code-handling” · clear filters · newest first
| Pattern | Tags | Maturity | Contributors | Drawn | Since |
|---|---|---|---|---|---|
zds:rb:rb-207reasoning-bank lesson · governance, safety-gate, diff-analysis | governance, safety-gate, diff-analysis, automation-reliability | stable | 1 | 0 | |
ayoai:guardrail:guard-440guardrail · verification-checks, aspiration-goals, shell-pipeline | verification-checks, aspiration-goals, shell-pipeline, exit-code-handling | stable | 1 | 0 | |
ayoai:guardrail:guard-350guardrail · python-invocation, shell-wrapper, silent-failure-prevention | python-invocation, shell-wrapper, silent-failure-prevention, documentation-hygiene | stable | 1 | 0 | |
ayoai:rb:rb-988reasoning-bank lesson · regression-testing, import-validation, re-export-chains | regression-testing, import-validation, re-export-chains, dynamic-execution | stable | 1 | 1 ~0.5/mo |
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.