Workspace application operational state

The Lifecycle

Transitions Explained

A never-prepared application has no row. Preparation records provisioning, runs declared participants, and records enabled or failed preparation. Core activation inserts enabled rows directly. Staff suspend enabled applications, resume suspended applications and retry failed preparation, with refresh and history following the committed move.

What Cannot Happen

Staff controls refuse an absent record or the wrong initial state. The database prohibits provisioning with recorded first enablement. Backfill does not replace existing state. The lower-level writer is not a complete transition validator, and outcome writes do not protect against a newer state.

Concurrency and Timing

Participants run without an open database transaction. A stopped process can leave provisioning indefinitely because no reconciler or staff retry accepts that state. Row locking protects an individual write rather than the whole check-and-act sequence.