Initial Load And Its Resets

The Lifecycle

Transitions Explained

This model combines workspace loading with reset-job standing; these labels are a projection rather than one stored enum. A reset stores its participant plan, removes resources in batches and leaves loading open on success. Failure retains partial removal, and recovery submits another reset. Activation ends loading independently of reset-job standing.

What Cannot Happen

Reset admission requires loading and implementation and permits only one pending or running reset. Activation is possible during or after failed reset because it checks no reset record. A later loading entry can replace the earlier opening facts on an active implementation workspace.

Concurrency and Timing

Reset creation rechecks the locked workspace, and each batch checks it again. Activation can race reset, making later batches refuse while exposing partial removal. The product should decide whether activation needs an additional reset safeguard and how to handle writes already in flight.