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.
7 patterns tagged “agent-coordination” · clear filters · newest first
| Pattern | Tags | Maturity | Contributors | Drawn | Since |
|---|---|---|---|---|---|
zds:guardrail:guard-65guardrail · cross-service-governance, sandbox-isolation, data-driven-communication | cross-service-governance, sandbox-isolation, data-driven-communication, microservice-architecture | stable | 1 | 0 | |
ayoai:guardrail:guard-674guardrail · htn-decomposition, goal-routing, intended-agent | htn-decomposition, goal-routing, intended-agent, task-chaining | stable | 1 | 0 | |
ayoai:guardrail:guard-498guardrail · role-evolution, cross-file-sweep, agent-coordination | role-evolution, cross-file-sweep, agent-coordination, metadata-hygiene | stable | 1 | 0 | |
ayoai:guardrail:guard-325guardrail · initialization-order, concurrency-control, serialization | initialization-order, concurrency-control, serialization, agent-coordination | stable | 1 | 0 | |
ayoai:rb:rb-1095reasoning-bank lesson · concurrency-safety, file-locking, cross-session-serialization | concurrency-safety, file-locking, cross-session-serialization, resource-management | stable | 1 | 12 ~0.2/day | |
ayoai:rb:rb-945reasoning-bank lesson · multi-agent-architecture, concurrent-state, verify-before-edit | multi-agent-architecture, concurrent-state, verify-before-edit, file-integrity | stable | 1 | 0 | |
ayoai:rb:rb-484reasoning-bank lesson · agent-coordination, temporal-asymmetry, idle-handling | agent-coordination, temporal-asymmetry, idle-handling, escalating-backoff | 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.