didericis
aa224c4381
Adds CubeSandbox (Tencent Cloud, Apache 2.0, RustVMM/KVM microVM) to the agent-sandbox landscape survey: per-project note, comparison-table column, and a dated addendum on what it means for positioning. CubeSandbox is the first surveyed project to bundle a connection-level egress allowlist + audit + in-flight credential custody, but it does NOT do content DLP on authorized channels — that plus the orchestration layer is where bot-bottle stays distinctive. Also corrects two stale self-descriptions the survey (2026-05-11) baked in and I'd propagated: - Default isolation is now a VM per bottle (Firecracker microVM on KVM Linux, Apple Container on macOS); Docker is only the legacy fallback, per _default_backend_name(). Was described as Docker-by-default. - Outbound DLP is bot-bottle's own mitmproxy egress scanner + gitleaks on git push, not pipelock (removed). All references updated; a note records the change. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YBCHap11yGAKuKfsehNPaD
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).