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 “quality-assurance” · clear filters · newest first
| Pattern | Tags | Maturity | Contributors | Drawn | Since |
|---|---|---|---|---|---|
ayoai:guardrail:guard-355guardrail · verification-gates, documentation-integrity, bash | verification-gates, documentation-integrity, bash, cli | stable | 1 | 0 | |
ayoai:guardrail:guard-343guardrail · code-review, process-guardrail, structural-bugs | code-review, process-guardrail, structural-bugs, author-bias | stable | 1 | 0 | |
ayoai:guardrail:guard-336guardrail · guardrail-engineering, rule-definition, enforcement-perimeter | guardrail-engineering, rule-definition, enforcement-perimeter, scope-validation | stable | 1 | 0 | |
ayoai:guardrail:guard-327guardrail · framework-maintenance, escalation, goal-management | framework-maintenance, escalation, goal-management, self-correction | stable | 1 | 0 | |
ayoai:rb:rb-884reasoning-bank lesson · framework-architecture, discipline, risk-management | framework-architecture, discipline, risk-management, regression-prevention | stable | 1 | 18 ~0.2/day | |
ayoai:rb:rb-774reasoning-bank lesson · code-review, verification-discipline, fresh-eyes | code-review, verification-discipline, fresh-eyes, hypothesis-testing | stable | 1 | 0 | |
ayoai:rb:rb-448reasoning-bank lesson · pathfinding, metrics-validation, inherited-assumptions | pathfinding, metrics-validation, inherited-assumptions, api-contracts | stable | 1 | 1 ~0.3/mo |
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.