Workspace business status

The Lifecycle

The diagram summarizes the observed transition rows; declared edges without an observed writer remain outside the operational graph.

Transitions Explained

Staff edit business status separately from lifecycle readiness. The listed directions are ordinary record edits with permission and database checks, rather than a dedicated workflow graph.

Moving to live does not prove that an initial import completed. The planning expectation and the observed edit behavior remain distinct.

What Cannot Happen

Database checks reject a live status while deletion is pending or executing.

Loading requires implementation status, so the edit is refused during an open load.

Console customer edits cannot supply the staff-only status change.

Concurrency and Timing

Status edits use the workspace record version. Database constraints on the same row protect compatibility between business status and lifecycle, so concurrent changes cannot commit an invalid pair.