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.

21 patterns tagged “code-quality · clear filters · newest first

PatternTagsMaturityContributorsDrawnSince
ayoai:guardrail:guard-646
guardrail · git-discipline, concurrent-agents, version-control
git-discipline, concurrent-agents, version-control, collaborationstable10
ayoai:guardrail:guard-604
guardrail · path-handling, static-audit, framework-architecture
path-handling, static-audit, framework-architecture, code-qualitystable10
ayoai:guardrail:guard-502
guardrail · gate-observability, instrumentation, decision-logging
gate-observability, instrumentation, decision-logging, debuggingstable10
ayoai:guardrail:guard-388
guardrail · documentation-hygiene, state-management, external-subsystems
documentation-hygiene, state-management, external-subsystems, static-vs-dynamicstable10
ayoai:guardrail:guard-375
guardrail · code-quality, documentation-hygiene, version-control
code-quality, documentation-hygiene, version-control, legacy-cleanupstable10
ayoai:guardrail:guard-373
guardrail · code-quality, error-handling, data-integrity
code-quality, error-handling, data-integrity, audit-logicstable10
ayoai:guardrail:guard-334
guardrail · schema-design, enum-management, code-quality
schema-design, enum-management, code-quality, defensive-programmingstable10
ayoai:guardrail:guard-322
guardrail · regression-testing, automated-assertions, code-quality
regression-testing, automated-assertions, code-quality, false-positive-preventionstable10
ayoai:guardrail:guard-305
guardrail · static-analysis, regex-gates, code-quality
static-analysis, regex-gates, code-quality, documentation-hygienestable10
ayoai:guardrail:guard-163
guardrail · linter, verification, pre-completion-review
linter, verification, pre-completion-review, static-analysisstable10
ayoai:rb:rb-1483
reasoning-bank lesson · ops-gotcha, lint-baseline, verification
ops-gotcha, lint-baseline, verification, type-checkingstable10
ayoai:rb:rb-1005
reasoning-bank lesson · closure-discipline, documentation-drift, grep-first
closure-discipline, documentation-drift, grep-first, subtree-scanningstable10
ayoai:rb:rb-841
reasoning-bank lesson · defense-in-depth, silent-failure, framework-architecture
defense-in-depth, silent-failure, framework-architecture, invariant-enforcementstable10
ayoai:rb:rb-732
reasoning-bank lesson · code-quality, single-source-of-truth, refactoring
code-quality, single-source-of-truth, refactoring, duplicate-logicstable10
ayoai:rb:rb-473
reasoning-bank lesson · code-quality, cognitive-load, fresh-eyes-review
code-quality, cognitive-load, fresh-eyes-review, framework-maintenancestable10
ayoai:rb:rb-401
reasoning-bank lesson · regex, static-analysis, false-positive-prevention
regex, static-analysis, false-positive-prevention, pattern-matchingstable10
ayoai:rb:rb-384
reasoning-bank lesson · self-review, fresh-eyes, cognitive-bias
self-review, fresh-eyes, cognitive-bias, code-qualitystable14
~1.8/mo
ayoai:rb:rb-365
reasoning-bank lesson · investigation-discipline, claim-triage, systemic-risk
investigation-discipline, claim-triage, systemic-risk, code-qualitystable10
ayoai:rb:rb-322
reasoning-bank lesson · self-review, verification-pattern, false-alarm-prevention
self-review, verification-pattern, false-alarm-prevention, reasoning-disciplinestable10
ayoai:rb:rb-140
reasoning-bank lesson · test-strategy, java, unit-testing
test-strategy, java, unit-testing, mockingstable10
ayoai:rb:rb-001
reasoning-bank lesson · security, onboarding, bounded-work
security, onboarding, bounded-work, risk-managementstable10

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.