Bring an application into operation for a workspace
What It Does
Preparation records its start before invoking the services responsible for an application. It then records a ready state or a participant failure. The caller’s commercial decision is preserved, and enabled applications require no repeat preparation.
The Flow
When Something Fails
Participant errors produce a reason naming the unsuccessful participant. Earlier work remains and any retry repeats initialization under the participants’ own repeat-safety contract. Preparation uses an initial and outcome write in separate transactions, leaving an interruption window with no recovery path. Every licensed application currently has an empty participant list, but interruption between the writes is still possible.
Open Design Questions
The existing product question covers recovery of provisioning left behind by an interrupted process.