State first
Every instance has a known lifecycle state. Support and operators can discuss pending, provisioning, active, suspended, failed, and deleted without guessing.
Solution path
Recoverable operations begin with explicit instance state.
BayStore makes the commercial lifecycle visible before runtime automation is fully wired, so retries, suspensions, upgrades, and restore intent are recorded instead of hidden in ticket notes.
Action record
Operator actions are recorded by the API; production runtime mutation remains deferred.
Recovery intent
Recovery copy names retries, restore requests, and rollback intent as lifecycle operations. It does not claim automated restore execution.
Operational model
Who owns what during the current launch boundary?
| Surface | Visible today | Deferred production dependency |
|---|---|---|
| Customer dashboard | Instance, plan, status, and sandbox access metadata. | Production identity, issued customer access URLs, and account authorization policy. |
| Operator console | Action records and deferred runtime mutation disclosure. | Worker-backed runtime execution, queue processing, secrets, and production clusters. |
| Security review | Static trust boundary, legal drafts, DPA link, and no public console navigation. | Approved controls, deployment-specific evidence, and any third-party certification claim. |
Certification boundary: BayStore does not currently claim SOC 2, ISO 27001, HIPAA, PCI DSS, or other third-party compliance certification.