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 “retry-strategy” · clear filters · newest first
| Pattern | Tags | Maturity | Contributors | Drawn | Since |
|---|---|---|---|---|---|
ayoai:guardrail:guard-670guardrail · infrastructure-migration, io-timeout, cutover-side-effects | infrastructure-migration, io-timeout, cutover-side-effects, false-positive-prevention | stable | 1 | 0 | |
ayoai:guardrail:guard-472guardrail · fileops, single-source-of-truth, atomic-write | fileops, single-source-of-truth, atomic-write, retry-strategy | stable | 1 | 0 | |
ayoai:rb:rb-1480reasoning-bank lesson · daemon-contention, timeout-masks-success, idempotency | daemon-contention, timeout-masks-success, idempotency, verify-before-assuming | 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 | 7 ~0.1/day | |
ayoai:rb:rb-974reasoning-bank lesson · ops-gotcha, json-decoding, daemon-corruption | ops-gotcha, json-decoding, daemon-corruption, diagnostics | 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.