didericis
ce440fabc4
OneCLI (onecli.sh) was already tracked in the credential-proxy landscape but the entry was stale (May 2026). Correct it: it uses the phantom-token pattern this note recommends (not "Bitwarden integration"), and it's now GA, Rust, YC-backed (~2.5k stars, 300k+ downloads). Add build-vs-adopt + competitor commentary, and a product-side entry in the containerized-claude landscape with a verdict on how close a competitor it is and where bot-bottle's edge lies (isolation as the product, fleet/manifest layer, self-hosted trust posture). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LhiafsABCr46bu3oHUm7wa
Docs
How this project records what it builds and why — and a guide to picking the right document for what you're capturing.
When to write which document
| Artifact | For |
|---|---|
PRD (docs/prds/) |
A feature: what to build, scope, success criteria. |
Research note (docs/research/) |
A landscape/tradeoff investigation. |
Decision record (docs/decisions/) |
A decision that isn't itself a feature — a policy, a convention, a "we will / won't do this," or a load-bearing choice made inside a larger PRD that deserves to be discoverable on its own. |
A decision that's fully specified by a PRD doesn't need duplicating in a decision record. Write one when the decision would otherwise be buried in prose, lost in an issue thread, or have no in-repo home at all (small requests that don't merit a PRD; non-feature choices like merge strategy or a trust posture).