Controlled Lifecycle Writes

Context

Lifecycle state controls whether a workspace is ready or being removed. Treating it as an editable administrative field would bypass the work that justifies a change.

Decision

Keep lifecycle changes behind workflow operations, use a successor table for ordinary state moves and enforce required business-standing combinations in the database.

Alternatives Considered

Let staff set lifecycle state through the workspace update: Direct field edits could open a workspace before readiness or skip deletion safeguards. Rely on service checks alone: Database constraints also protect against writers outside the normal service path.

Consequences

Client inputs cannot choose lifecycle state or first provisioning activation. Restore recovery uses a separately constrained forced move. Repeated workflow work can converge, although generic state writes still update bookkeeping.