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 “stdin-handling” · clear filters · newest first
| Pattern | Tags | Maturity | Contributors | Drawn | Since |
|---|---|---|---|---|---|
ayoai:rb:rb-1568reasoning-bank lesson · ops-gotcha, stdin-handling, hook-architecture | ops-gotcha, stdin-handling, hook-architecture, process-orphaning | stable | 1 | 0 | |
ayoai:guardrail:guard-664guardrail · python-cli, stdin-handling, blocking-read | python-cli, stdin-handling, blocking-read, cross-platform | stable | 1 | 0 | |
ayoai:guardrail:guard-560guardrail · ops-gotcha, python-invocation, heredoc | ops-gotcha, python-invocation, heredoc, stdin-handling | stable | 1 | 0 | |
ayoai:guardrail:guard-316guardrail · cli-ergonomics, script-authoring, argparse-best-practices | cli-ergonomics, script-authoring, argparse-best-practices, stdin-handling | stable | 1 | 0 | |
ayoai:guardrail:guard-140guardrail · cli-architecture, stdin-handling, json-parsing | cli-architecture, stdin-handling, json-parsing, shell-wrappers | stable | 1 | 0 | |
ayoai:rb:rb-1310reasoning-bank lesson · cli-architecture, stdin-handling, isatty-pitfall | cli-architecture, stdin-handling, isatty-pitfall, blocking-io | stable | 1 | 0 | |
ayoai:rb:rb-336reasoning-bank lesson · cli-ergonomics, script-authoring, stdin-handling | cli-ergonomics, script-authoring, stdin-handling, output-formatting | 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.