Tide chart
The single-tenant instance lifecycle gives every buyer-visible deployment a name and state.
BayStore's product-instance model is useful because the commercial record, access boundary, and operational state stay connected from purchase through retirement.
Lifecycle states
The state tokens are intentionally small.
pendingprovisioningactiveupgradingsuspendedfaileddeleted
PendingThe commercial record exists, but the instance has not reached a provisioning step.
ProvisioningBayStore records desired state and tracks readiness against the M100 evidence path.
ActiveThe instance is visible as usable within the current boundary. Access metadata reflects the sandbox/test-runtime boundary unless a separate production deployment is completed.
FailedFailure is represented as a state so retries and support work do not overwrite history.
Suspended or deletedCommercial and support context stays visible while access and lifecycle actions are restricted.
Buyer visibility
What a buyer can infer from the lifecycle.
| Visible item | Meaning | Current boundary |
|---|---|---|
| Product and berth | The product family and capacity marker the buyer selected. | Berth prices are static marketing copy until provider billing is configured. |
| Status | The named lifecycle state shared across public copy, dashboard, and operator records. | Status is evidence context; it does not by itself prove full production readiness. |
| Access metadata | A reference for where a buyer would access the instance. | Access metadata reflects the sandbox/test-runtime boundary unless a separate production deployment is completed. |
| Recovery language | Retry, restore intent, suspension, and deletion are explicit actions. | Runtime action evidence is represented through the bounded non-payment launch packet. |
Checkout boundary: Checkout remains
sandbox_placeholder; this public site does not charge cards or configure production provider billing.