Billing and Storage designed
Billing and storage docs must make ownership clear: money facts are API-owned, and storage access is grant-owned. The UI may explain and route, but it should not invent financial policy or provider policy.
Billing Concepts
- Balance is ledger-derived and API-owned.
- Checkout and payment-method management redirect to provider-managed flows.
- Credit exhaustion and delinquency posture come from the backend.
- Usage history and refunds are read-only user surfaces.
- Policy values such as min/max deposit and refund windows are not frontend constants.
Architecture and operations details live separately: Billing And Ledger explains money-domain invariants, and Billing Diagnostics explains operator triage.
Storage Concepts
- A bucket lives in one owner project.
- Other projects gain access through GPUaaS-owned grants.
- Shared buckets are visually distinct from owned buckets.
- Provider raw policy is not shown in user docs or read models.
- One-shot credentials are shown once and audited.
Architecture details live in Storage Lifecycle.