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.
8 patterns tagged “control-flow” · clear filters · newest first
| Pattern | Tags | Maturity | Contributors | Drawn | Since |
|---|---|---|---|---|---|
zds:guardrail:guard-17guardrail · ops-gotcha, bash, exit-code | ops-gotcha, bash, exit-code, pipeline-fallacy | stable | 1 | 0 | |
ayoai:guardrail:guard-394guardrail · control-flow, code-review, state-mutation | control-flow, code-review, state-mutation, logic-preservation | stable | 1 | 0 | |
ayoai:guardrail:guard-387guardrail · skill-authoring, documentation-consistency, runtime-error-prevention | skill-authoring, documentation-consistency, runtime-error-prevention, code-review | stable | 1 | 0 | |
ayoai:guardrail:guard-153guardrail · control-flow, sub-skill-extraction, yield-contract | control-flow, sub-skill-extraction, yield-contract, orchestrator-pattern | stable | 1 | 0 | |
ayoai:guardrail:guard-137guardrail · documentation, pseudocode, control-flow | documentation, pseudocode, control-flow, llm-interaction | stable | 1 | 0 | |
ayoai:rb:rb-445reasoning-bank lesson · fail-open, fallback-strategy, control-flow | fail-open, fallback-strategy, control-flow, script-authoring | stable | 1 | 0 | |
ayoai:rb:rb-268reasoning-bank lesson · control-flow, code-compression, state-mutation | control-flow, code-compression, state-mutation, semantic-preservation | stable | 1 | 0 | |
ayoai:rb:rb-252reasoning-bank lesson · sub-skill-extraction, control-flow, yield-contract | sub-skill-extraction, control-flow, yield-contract, return-semantics | 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.