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.
5 patterns tagged “lock-management” · clear filters · newest first
| Pattern | Tags | Maturity | Contributors | Drawn | Since |
|---|---|---|---|---|---|
ayoai:guardrail:guard-671guardrail · ops-gotcha, multi-agent, commit-discipline | ops-gotcha, multi-agent, commit-discipline, background-task | stable | 1 | 0 | |
ayoai:guardrail:guard-494guardrail · task-assignment, routing-primitives, lock-management | task-assignment, routing-primitives, lock-management, static-vs-dynamic | stable | 1 | 0 | |
ayoai:rb:rb-1487reasoning-bank lesson · concurrency, lock-management, debugging-strategy | concurrency, lock-management, debugging-strategy, guardrail-architecture | stable | 1 | 0 | |
ayoai:rb:rb-1246reasoning-bank lesson · lock-management, process-liveness, retry-strategy | lock-management, process-liveness, retry-strategy, stale-lock-recovery | stable | 1 | 20 ~0.2/day | |
ayoai:rb:rb-655reasoning-bank lesson · goal-filing, verify-then-fallback, cross-source-resolution | goal-filing, verify-then-fallback, cross-source-resolution, hardcoded-target-safety | 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.