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 “state-persistence” · clear filters · newest first
| Pattern | Tags | Maturity | Contributors | Drawn | Since |
|---|---|---|---|---|---|
ayoai:guardrail:guard-621guardrail · content-stable-keys, cross-iteration-memory, state-persistence | content-stable-keys, cross-iteration-memory, state-persistence, test-coverage-gap | stable | 1 | 0 | |
ayoai:guardrail:guard-571guardrail · goal-management, state-persistence, ttl-misconfiguration | goal-management, state-persistence, ttl-misconfiguration, human-in-the-loop | stable | 1 | 0 | |
ayoai:guardrail:guard-448guardrail · framework-maintenance, loop-state, state-persistence | framework-maintenance, loop-state, state-persistence, counter-drift | 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.