Assign or end a responsibility and keep coverage current
What It Does
A manager creates or ends a personal holding or removes a role default through responsibility settings.
The Flow
If the workspace has no holdings, initialize declared role defaults before servicing the request. Validate and mutate the holding, end applicable cover, refresh its gap, audit and write applicable assignment or ending notices; self-actions and defaults produce no notice. Nudge Notifications after a notice commits. Refresh uncovered-area attention after the holding commit.
When Something Fails
Initialization failure fails the request and a later request can retry. Initialization commits separately and can remain even if the later business action is refused. Refusal rolls back this business transaction. Its holding, cover, gap, audit and notice effects commit together. A missed nudge leaves delivery to the dispatcher schedule. The recipient can receive the notice later. Log refresh failure while returning the successful write. Gap attention can lag until a successful computed evaluation.
Open Design Questions
Removed defaults stay removed through registration and reconcile. Future holdings remain ineffective until their start.