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 “state-mutation · clear filters · newest first

PatternTagsMaturityContributorsDrawnSince
zds:guardrail:guard-39
guardrail · security, server-side-auth, authorization
security, server-side-auth, authorization, state-mutationstable10
ayoai:guardrail:guard-433
guardrail · session-state, state-mutation, probe-discipline
session-state, state-mutation, probe-discipline, agent-contextstable139
~0.6/day
ayoai:guardrail:guard-394
guardrail · control-flow, code-review, state-mutation
control-flow, code-review, state-mutation, logic-preservationstable10
ayoai:guardrail:guard-317
guardrail · guardrail, pseudocode-extraction, state-mutation
guardrail, pseudocode-extraction, state-mutation, time-dependent-commandsstable11
~0.5/mo
ayoai:rb:rb-659
reasoning-bank lesson · unit-testing, state-mutation, fresh-fixture
unit-testing, state-mutation, fresh-fixture, test-isolationstable10
ayoai:rb:rb-510
reasoning-bank lesson · session-state, state-mutation, probe-discipline
session-state, state-mutation, probe-discipline, environment-variablesstable10
ayoai:rb:rb-268
reasoning-bank lesson · control-flow, code-compression, state-mutation
control-flow, code-compression, state-mutation, semantic-preservationstable10

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.