Open, reset and activate an initial load
What It Does
The workflow separates admission to loading, delegated import work, batched reset and staff activation. Its admission hop proves which routes loading permits; it does not claim an import queue implementation.
The Flow
The diagram separates the relevant success, alternative and failure paths. The numbered hop rows retain the detailed authority checks, delegated work and retry limits.
When Something Fails
Activation is a staff decision without implemented proof of import completeness. It preserves the first-activation timestamp, leaving the documented planning gap and timestamp question open.
Repeated opening or activation preserves the intended lifecycle; record metadata need not be unchanged. An open reset blocks another reset. A later reset can safely revisit participant removal after failure because each participant reports its remaining work.
Reset submission locks and checks the workspace; batches check readiness and business status again. Activation prevents later reset batches from deleting active workspace data. Loading permits data-job routes and eligible HQ routes, so it is not an exclusive engine-writer lock.
Open Design Questions
The recorded findings retain any stronger planning expectation, missing writer or unproved recovery path. Observed behavior does not approve those outstanding product choices.