didericis
23015f7fd8
Verdict-first research note on whether bot-bottle has a defensible paid wedge in the 2026 field. Consolidates the agent-provider-agnostic framing, the Fly remote-backend idea, the supervisor/egress-audit play, and the solo-dev/Linux brand instinct. Conclusion: the only defensible position is the bundle no competitor occupies — uniform egress audit + secret custody + policy across heterogeneous coding agents, on your infra or a managed pool. Isolation and OSS/self-host are commodity; the buyer is teams, not solo devs; mobile remote/launch is already commoditized by the Pi ecosystem (Paseo et al.). Sell cross-vendor fleet governance to teams; use the indie brand as the funnel. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NkwFXLFff9PYPy4wgVBJp9
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).