Install and reset the baseline activity and task types
What It Does
CRM declares baseline configuration and lifecycle participants so workspaces can start with usable activity and task categories. Seed adoption preserves local administration. Reset and purge have different retention goals and operate through their declared cleanup steps.
The Flow
The numbered hops specify the request, persistence and integration boundaries in order. Each hop identifies its evidence anchor, synchronization seam and observable failure outcome. Branches distinguish optional and delegated paths.
When Something Fails
A participant reports failed steps to its lifecycle caller. Earlier committed steps can remain applied, with seed-ledger behavior supporting repeat provisioning. External participant registration and orchestration recovery remain unverified rather than presumed missing.
Open Design Questions
Platform must supply evidence of participant registration and reconciliation for existing workspaces before provisioning and cleanup readiness can be accepted.