Workspace Lifecycle

The Lifecycle

Transitions Explained

Construction opens the workspace after readiness, or leaves it in failed-provisioning standing for staff recovery. A retry returns it to construction through a new linked attempt. Staff can open loading on an active implementation workspace and activate it afterward without changing business standing.

A removal request moves an eligible disabled workspace to pending deletion. Cancellation returns lifecycle to active but keeps the workspace disabled. Irreversible-removal checks commit deleting lifecycle with the purge job. Restore recovery is a separate forced move backed by the external ledger.

What Cannot Happen

The ordinary successor table rejects skipped construction and reversed destruction. Restore reapplication is an exception that can force deleting from any restored state. Although loading can precede pending deletion in the table, the current deletion request cannot admit that combination.

Concurrency and Timing

Lifecycle services lock and inspect the workspace row. The successor assertion accepts the same state, but a generic state write can still increment record version and modification facts. Availability caches in other processes can retain earlier facts for thirty seconds. HQ updates outside the workspace gate remain a separate write boundary.