Rhythm 2.0 Specifications

Appearance

WF-CRM-ACT-007Carry activities and tasks through record merge and deletion

Markdown

WF-CRM-ACT-007

Carry activities and tasks through record merge and deletion

Markdown
  • DocumentDraft
  • ImplementationPartially observed

Planning

Implements
CAP-CRM-ACT-018, CAP-CRM-ACT-005

KindWorkflowProduct areaCRMModuleActivities, Follow-ups and Task WorkRevision1

Read atservices-crm a8d1364freact-console baf6dae3

Carry activities and tasks through record merge and deletion ​

What It Does ​

Interactions and work survive the removal of related context. Merge transfers that context to a survivor; deletion removes only the corresponding associations or references. Activity provides its own merge-transfer implementation, while the shared merge policy changes task references directly.

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 ​

Merge and deletion each roll back their own database changes on failure. Successful deletion can intentionally leave an interaction without any visible timeline or primary link. The planned authorized orphan-management and deletion-audit behavior remains unimplemented, and direct task reference changes can leave attention context stale.

Open Design Questions ​

Product’s retained-interaction management decision still needs a screen and authorized operation. The acceptable stale attention context after merge or deletion also needs implementation treatment.

Controls

30 controls apply, from the corpus control catalogue.

TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-AZ-005 TC-AZ-006 TC-DAT-001 TC-DAT-002 TC-DAT-003 TC-DAT-004 TC-IAM-001 TC-IAM-005 TC-IAM-006 TC-LOG-001 TC-LOG-002 TC-LOG-003 TC-LOG-004 TC-LOG-005 TC-MON-001 TC-MON-002 TC-PI-001 TC-PI-003 TC-PI-004 TC-PI-005 TC-PRV-001 TC-PRV-002 TC-PRV-003 TC-TEN-001 TC-TEN-002 TC-TEN-003

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.

Rhythm Software