Provision a workspace
What It Does
Provisioning commits intent before invoking participant work. The hop rows identify validation, durable submission, participant execution, readiness, activation and failure settlement.
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
Failure retains completed preparation rather than compensating it away. A retry resumes from the copied completed steps. Notification claims and provider sends have different guarantees; successful activation does not prove every completion notice arrived.
The wizard retains a submission identity across repeats, returning the existing workspace and job. A competing submission cannot take an occupied identifier. Retry carries completed steps forward; participants use their seed ledgers to converge. Notification claims avoid repeating a claim, but a failed send after claiming can leave a recipient uninformed.
Submission commits customer creation when requested, the workspace and its job together. Participant execution follows dependency order. Initialization accepts active or failed-provisioning workspaces, while retirement excludes a still-running provisioning state.
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.