didericis-claude
814c7338a1
- Broaden scope from "Claude Code in Docker" to "AI coding agents in isolated sandboxes" - Add SuperHQ (superhq.ai, v0.4.4) as a new adjacent-competitor entry: macOS-only microVM desktop app, overlaps on isolation/credential-proxy/multi-provider but has no manifest layer and no audit logging - Note SuperHQ's user-voiced audit gap (Brian Cheong, Dunialabs.io) and that bot-bottle already covers it - Update differentiation list to reflect three backends (Docker, Apple container, smolmachines) and three built-in providers (Claude Code, Codex, Pi) plus plugin system - Add in-flight directions for forge-native dispatch (#317) and paid web control plane (#327) with honest framing: lifecycle concept is not novel vs. cloud services (Devin, Copilot Workspace); differentiation is self-hosted + manifest-driven + stronger isolation
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).