Recipe
Object storage is a destination boundary, not a privacy shortcut.
Use this recipe to document the difference between local MinIO, private network object storage, and public cloud S3/R2 delivery. VoxNotch can support destination workflows, but the operator owns the boundary decision.
- Local rehearsal
- MinIO or local destination path
- Cloud destination
- S3/R2 credentials and bucket policy
- Egress
- Explicit when destination is outside the host/network
Boundary map
The same destination shape can mean different custody.
| Destination | What to prove | What not to claim |
|---|---|---|
| Local filesystem | Allowed destination path exists, is writable by the service, and is covered by backup. | Do not claim remote durability unless a separate backup proof exists. |
| Local MinIO | Bucket exists on your local stack or private network, credentials are scoped, and backup covers the object store. | Do not describe it as cloud storage just because it speaks an S3-compatible API. |
| S3 or R2 | Bucket policy, credentials, region/account owner, lifecycle rules, and an explicit egress decision. | Do not call the workflow fully local after artifacts leave the instance. |
This table describes custody boundaries only. It does not compare vendor durability, pricing, compliance, or performance.
Proof template
destination-proof.txt
Destination type: local-filesystem | local-minio | s3 | r2
Bucket or path:
Network boundary: none | private-network | public-cloud
Credential scope:
Backup coverage:
Lifecycle/delete policy:
Last proof artifact:
Operator sign-off:Keep secrets out of the proof. The useful evidence is the boundary decision, the artifact path, and the restore story.