Workspace Lifecycle
What It Models
Workspace readiness and removal standing are system facts on the administrative workspace record. They control request availability separately from the customer’s business standing.
Identity and Attributes
This object uses the workspace’s permanent identifier and has no independent record identity. System-owned construction, active, loading or removal standing; direct creation defaults active. Administrative live, implementation or disabled standing, constrained against loading and removal lifecycle. The first provisioning activation stamp; absence selects unopened treatment unless disposable policy takes precedence. Latest load-opening time, required while loading and retained by activation. Staff actor for the latest opening, required while loading. An optional opening explanation bounded to five hundred characters. A false-by-default test designation for accelerated non-Production removal. A request-specific available, unavailable or read-only result from cached workspace facts and route context. The local diagnostic reason for a uniform unavailable response.
Relationships
Workspace administration owns the shared row; lifecycle owns the system facts. The attempt retains its workspace reference. Loading facts occupy the same workspace record. The request retains copied identity without depending on the workspace row.
Invariants
The structured invariants distinguish service and database enforcement from documented obligations. The listed enforcement points bound what the workflow can rely on.
How It Is Stored and Shared
Platform’s lifecycle service owns this design object. The physical declarations identify its stored records, while shared jobs provide durable execution and inspection.
Open Design Questions
Availability copies and HQ writes outside the gate limit a universal access claim. Restore reapplication remains necessary because the gate does not read the external deletion ledger.