1fb524cc1a
test / stage-firecracker-inputs (pull_request) Successful in 6s
test / unit (pull_request) Failing after 34s
test / integration-docker (pull_request) Failing after 34s
tracker-policy-pr / check-pr (pull_request) Failing after 35s
test / build-infra (pull_request) Failing after 32s
test / integration-firecracker (pull_request) Has been skipped
test / coverage (pull_request) Has been skipped
test / publish-infra (pull_request) Has been skipped
Investigates storage candidates, retention policy design, and image-size reduction techniques in response to the PR #459 comment on a secure remote store for committed Firecracker snapshots.
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).