The activities participant declares the baseline catalog for workspace setup. Its seed application creates missing entries or adopts existing matching records. Adoption preserves the customer’s configured values. Built-in codes distinguish standard categories from custom ones. Staff can rename or deactivate a baseline type within the allowed configuration rules. They cannot delete it or change its established code. Call and Email keep direction as a required detail. Platform must register and run the participant for provisioning and reconciliation to take effect. The product should verify that integration before claiming coverage across deployed workspaces.
8 rules, 6 to be proved before approval. A rule's product intent is derived from its origin: 1 confirmed by a product decision, the rest inheriting this capability's proposed.
Id
Rule
Kind
Enforced at
Provenance
01must prove
Proposed
The activities participant declares seven baseline activity types, while workspace-wide installation depends on Platform registering that participant.