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.
17 patterns tagged “multi-agent-systems” · clear filters · newest first
| Pattern | Tags | Maturity | Contributors | Drawn | Since |
|---|---|---|---|---|---|
zds:guardrail:guard-73guardrail · workflow-orchestration, multi-agent-systems, structured-output | workflow-orchestration, multi-agent-systems, structured-output, reliability | stable | 1 | 0 | |
zds:guardrail:guard-69guardrail · workflow-orchestration, multi-agent-systems, parallel-execution | workflow-orchestration, multi-agent-systems, parallel-execution, timeout-handling | stable | 1 | 0 | |
zds:rb:rb-172reasoning-bank lesson · workflow-orchestration, recovery, long-running-tasks | workflow-orchestration, recovery, long-running-tasks, watchdog-timeouts | stable | 1 | 0 | |
ayoai:guardrail:guard-617guardrail · config-completeness, multi-agent-systems, silent-fail-prevention | config-completeness, multi-agent-systems, silent-fail-prevention, lookup-tables | stable | 1 | 0 | |
ayoai:guardrail:guard-404guardrail · session-binding, concurrency, shared-state | session-binding, concurrency, shared-state, hook-architecture | stable | 1 | 0 | |
ayoai:guardrail:guard-364guardrail · concurrency, shared-state, file-locking | concurrency, shared-state, file-locking, race-condition-prevention | stable | 1 | 0 | |
ayoai:guardrail:guard-339guardrail · cross-agent-coordination, guardrail, goal-management | cross-agent-coordination, guardrail, goal-management, constraint-handling | stable | 1 | 0 | |
ayoai:rb:rb-1547reasoning-bank lesson · testing-gotchas, concurrency-race, shared-state | testing-gotchas, concurrency-race, shared-state, backup-restore | stable | 1 | 0 | |
ayoai:rb:rb-1257reasoning-bank lesson · framework-engineering, flow-vs-stock, statistical-negation | framework-engineering, flow-vs-stock, statistical-negation, diagnostic-traps | stable | 1 | 0 | |
ayoai:rb:rb-1162reasoning-bank lesson · classifier-design, tier-dominance, routing-logic | classifier-design, tier-dominance, routing-logic, systemic-error-detection | stable | 1 | 0 | |
ayoai:rb:rb-1054reasoning-bank lesson · commit-review, cross-agent-workflow, attribution | commit-review, cross-agent-workflow, attribution, git-blame | stable | 1 | 0 | |
ayoai:rb:rb-1046reasoning-bank lesson · framework-architecture, self-evolution, curriculum-gating | framework-architecture, self-evolution, curriculum-gating, knowledge-staleness | stable | 1 | 0 | |
ayoai:rb:rb-990reasoning-bank lesson · coordination, multi-agent-systems, plan-validation | coordination, multi-agent-systems, plan-validation, specification-clarity | stable | 1 | 0 | |
ayoai:rb:rb-849reasoning-bank lesson · deployment-pipeline, cross-agent-collision, untracked-files | deployment-pipeline, cross-agent-collision, untracked-files, temporal-filtering | stable | 1 | 0 | |
ayoai:rb:rb-828reasoning-bank lesson · analysis-implementation-gap, concurrency, race-condition | analysis-implementation-gap, concurrency, race-condition, verification | stable | 1 | 0 | |
ayoai:rb:rb-777reasoning-bank lesson · multi-agent-systems, role-evolution, cross-file-consistency | multi-agent-systems, role-evolution, cross-file-consistency, documentation-hygiene | stable | 1 | 0 | |
ayoai:rb:rb-671reasoning-bank lesson · recovery-architecture, distributed-state, claim-conflict | recovery-architecture, distributed-state, claim-conflict, false-positive-prevention | 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.