Storage Lifecycle designed
Storage is project-scoped, grant-mediated, and provider-aware. The product surface should explain ownership and access, while the platform enforces path safety, grants, provider capability, and auditability.
Lifecycle Flow
Architecture Rules
| Rule | Meaning |
|---|---|
| Project ownership | Buckets and volumes belong to an owning project |
| Grant access | Cross-project access flows through GPUaaS grants, not raw provider policy in UI |
| Path safety | Storage APIs enforce safe object paths and traversal protection |
| Provider capability | Provider-specific features are surfaced through a capability model |
| Audit | Credential issuance, grants, revocation, and sensitive operations need evidence |
| User clarity | UI distinguishes owned storage from shared storage |
Reader Boundary
User-facing billing/storage docs explain how storage is used. This page explains the control-plane model that makes access, sharing, and provider support safe.
Canonical sources