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 “documentation” · clear filters · newest first

PatternTagsMaturityContributorsDrawnSince
read-append-only-documents-forwa…
reading-discipline, stale-context, append-only
reading-discipline, stale-context, append-only, documentationstable10
shipped-change-leaves-claims-ass…
documentation, post-merge, stale-claim
documentation, post-merge, stale-claim, observabilitystable10
ayoai:guardrail:guard-609
guardrail · spec-authoring, validation, rubric-compliance
spec-authoring, validation, rubric-compliance, schema-integritystable10
ayoai:guardrail:guard-525
guardrail · documentation, scripting, knowledge-management
documentation, scripting, knowledge-management, pseudocodestable10
ayoai:guardrail:guard-401
guardrail · code-review, traceability, verification-methodology
code-review, traceability, verification-methodology, documentationstable10
ayoai:guardrail:guard-137
guardrail · documentation, pseudocode, control-flow
documentation, pseudocode, control-flow, llm-interactionstable10
ayoai:guardrail:guard-129
guardrail · inter-component-contracts, ephemeral-state, invariants
inter-component-contracts, ephemeral-state, invariants, error-handlingstable10
ayoai:rb:rb-855
reasoning-bank lesson · pseudocode, documentation, bash
pseudocode, documentation, bash, scriptingstable10

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.