Retain interactions and work through record deletion and merge

Purpose

CRM record changes preserve related work and move appropriate references to a survivor.

How It Works

An administrator removes a contact or organization through the owning records module. Storage removes the activity links to that record. Activities with other links still appear in those contexts. An activity with no links remains stored but its console link has no record to open. The deletion journey inspects whether removed links appear in the audit. A merge uses the activities module’s reference-handling helpers to move and collapse links. Task references move to the survivor through the merge process. Preview versions help detect activity changes after planning. A merged record’s timeline directs callers to the survivor. The product should finish the recorded orphan-management and deletion-audit requirements.

Relationships

Task recording defines survival after a related record is deleted.
Activity logging owns the links transferred by merge.
Entities owns record deletion, and Data Quality owns merge orchestration.

Show evidence (sources, provenance, origins, pinned commits)

The Formal Contract

The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.

Outcomes: Shared activity links retained where possibleTasks moved to the merged survivorUnlinked activity retention made visible as a gap
Surfaces: apijob
Intent sources: services-crm:docs/milestones/CRM-M8-activities-and-tasks.md#D-44services-crm:docs/milestones/CRM-M4-duplicates-and-merge.md#D-20

Controls

27 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-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

Permissions

Key	Checked at	Scope
`crm.contacts.merge`	service	tenant
`crm.organizations.merge`	service	tenant
`crm.contacts.delete`	service	tenant

Business Rules

8 rules, 8 to be proved before approval. A rule's product intent is derived from its origin: 3 confirmed by a product decision, the rest inheriting this capability's proposed.

Id	Rule	Kind	Enforced at	Provenance
`01`must prove Proposed	Deleting a related record removes its activity links only, preserving the activity on other linked records’ timelines. no proof recorded yet	lifecycle	database	test services-crm:modules/activities/tests/integration/services/persistence/activities.integration.spec.js#leaves the activity on the other records’ timelines when one linked contact is deleted
`02`must prove Proposed	An activity left without links retains direct and authorized dataset access but has no timeline and cannot open through its console record link. no proof recorded yet	lifecycle	database	observed services-crm:modules/activities/queries/activities.query.ts:activitiesQuery; react-console:app/(console)/console/[tenantId]/crm/activities/[id]/page.tsx
`03`must prove Confirmed	Loss of the final related record neither deletes the activity nor automatically transfers it to an organization. origin: services-crm:docs/milestones/CRM-M8-activities-and-tasks.md#D-44 no proof recorded yet	policy	database	test react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0719.spec.ts#CRM-ACC-0719
`04`must prove Proposed	The deletion journey checks for removed activity links in the audit and records an absent section as a gap, without proving the same gap in every deployment. no proof recorded yet	policy	service	test react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0719.spec.ts#CRM-ACC-0719
`05`must prove Proposed	Merging transfers activity links to the survivor, collapses duplicate links and preserves a primary flag on the retained link. no proof recorded yet	calculation	service	test react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0720.spec.ts#CRM-ACC-0720
`06`must prove Confirmed	Merge preview evidence includes activity versions, allowing later activity changes to invalidate the plan. origin: services-crm:docs/milestones/CRM-M4-duplicates-and-merge.md#D-31 no proof recorded yet	invariant	service	observed services-crm:modules/activities/services/persistence/activities.ts:listActivityLinkVersionsOfRecords
`07`must prove Proposed	Merge transfers related task references to the surviving record. no proof recorded yet	calculation	service	test react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0720.spec.ts#CRM-ACC-0720
`08`must prove Confirmed	Reading a merged-away record’s timeline returns Gone with the surviving record reference. origin: services-crm:docs/milestones/CRM-M4-duplicates-and-merge.md#D-20 no proof recorded yet	validation	api	test react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0720.spec.ts#CRM-ACC-0720

Scenarios

Id	Given	When	Then	Provenance
`01`	Two contacts share a meeting and one also has a separate call.	Merge the duplicate into the survivor.	The survivor receives both activities without duplicate meeting links and retains the primary designation.	test react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0720.spec.ts#CRM-ACC-0720

Edge Cases

Id	Given	When	Then	Provenance
`02`	One contact is an activity’s only link and a task’s related person.	Delete that contact.	The activity has no links and the task remains with its contact reference cleared.	test react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0719.spec.ts#CRM-ACC-0719

Planning

Retain interactions and work through record deletion and merge ​

Purpose ​

How It Works ​

Relationships ​