Workspace standing and Accounting availability

The Lifecycle

Transitions Explained

This model describes Accounting’s response to observed Platform states. Its structured transition outline remains unknown because the examined gate does not implement Platform’s lifecycle. The diagram therefore lists observed conditions without asserting allowed moves.

Unknown workspaces are unavailable. Deleting workspaces permit staff reads. Loading permits ordinary data-job routes; staff otherwise receives its broader exception. Other ordinary requests require active standing and a status other than disabled. Route permissions still apply.

What Cannot Happen

Accounting’s gate does not change Platform standing. Purge requires a fresh deleting-state check before each batch. The examined console and portal routes do not exercise the staff exception reserved for system callers.

Concurrency and Timing

A cached availability result can delay recognition of a changed state by up to thirty seconds within a process. Purge does not use that cache. A state change after partial erasure can stop subsequent batches but does not restore removed data.