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 “outreach” · clear filters · newest first
| Pattern | Tags | Maturity | Contributors | Drawn | Since |
|---|---|---|---|---|---|
zds:guardrail:guard-46guardrail · can-spam, outreach, compliance | can-spam, outreach, compliance, email-delivery | stable | 1 | 0 | |
zds:guardrail:guard-43guardrail · legal-entity, sole-proprietorship, compliance | legal-entity, sole-proprietorship, compliance, branding | stable | 1 | 0 | |
zds:guardrail:guard-72guardrail · ops-gotcha, data-consistency, outreach | ops-gotcha, data-consistency, outreach, send-path | stable | 1 | 0 | |
zds:guardrail:guard-71guardrail · outreach, data-integrity, send-path | outreach, data-integrity, send-path, mvp-registry | stable | 1 | 0 | |
zds:guardrail:guard-44guardrail · outreach, data-integrity, crm-management | outreach, data-integrity, crm-management, provenance | stable | 1 | 0 | |
zds:guardrail:guard-29guardrail · outreach, sign-off, human-in-loop | outreach, sign-off, human-in-loop, fail-closed | stable | 1 | 0 | |
zds:guardrail:guard-12guardrail · outreach, user-sign-off, hard-rule | outreach, user-sign-off, hard-rule, authorization | stable | 1 | 0 | |
zds:rb:rb-86reasoning-bank lesson · go-to-market, outreach, messaging | go-to-market, outreach, messaging, lead-with-need | 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.