Inspect merge outcomes and attribution

Purpose

Staff can understand who requested a merge and what information and connections it changed.

How It Works

Merge-authorized readers open Recently Merged and filter the workspace history. Each entry identifies the participating records and requester in readable terms. Detail views preserve the original records and the survivor as written. Field outcomes explain the winning, losing and gap-filling sources. They retain decisions and related-record actions for later inspection. A record reader can inspect the successful merges that made that record without merge-management authority. Management-only details remain excluded from that narrower response. Aliases connect earlier absorbed identities to the same history. Merge records persist for the workspace lifetime and cannot be erased by ordinary application operations. The product should implement the promised removal of one person's original values on a privacy request. A merge itself is irreversible; repair uses ordinary editing or recreation.

Relationships

Execution produces attempts and permanent outcomes. Alias resolution joins an absorbed identity to the survivor's history. Platform owns audit pointers and workspace export delivery.

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: Retained originals support explanation and recreation after an incorrect merge.Record readers can inspect successful lineage and its originals.Merge-management readers can investigate workspace-wide attempts and outcomes.
Surfaces: consoleapi
Intent sources: services-crm:docs/milestones/CRM-M4-duplicates-and-merge.md#D-30services-crm:docs/milestones/CRM-M6-access-and-audit.md#D-21services-crm:docs/merging/decisions.md#D4 (decided 2026-10-11: option 1)services-crm:docs/merging/experience/functional-requirements.md#AUD-1 to AUD-3, DQ-9 (package approved by Andrew 2026-10-13)

Controls

20 controls apply, from the corpus control catalogue.

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

Permissions

Key	Checked at	Scope
`crm.merges.read`	api	tenant
`crm.contacts.read`	api	record
`crm.organizations.read`	api	record

Business Rules

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

Id	Rule	Kind	Enforced at	Provenance
`01`must prove Confirmed	Workspace history requires merge-read authority, lists newest first with succeeded as the default status, supports status/type/requester/date filters and defaults to 25 entries with a maximum of 50. origin: services-crm:docs/merging/experience/functional-requirements.md#AUD-3 no proof recorded yet	policy	api	test services-crm:modules/merges/tests/integration/services/merges/tenant-merge-history.integration.spec.js#answers the merges that succeeded, which is what a history screen asks for by default
`02`must prove Confirmed	Record history includes merges survived by the record and its absorbed identities, with equivalent results when requested through an alias. origin: services-crm:docs/merging/experience/functional-requirements.md#AUD-1 no proof recorded yet	policy	service	test services-crm:modules/merges/tests/e2e/merges.e2e.spec.js#answers the same history when asked under an id the merge took away, under the survivor
`03`must prove Confirmed	History uses participant names and numbers captured at merging and the requester's current name, leaving unavailable names blank rather than displaying internal identities. origin: services-crm:docs/merging/experience/functional-requirements.md#DQ-9 no proof recorded yet	policy	service	test services-crm:modules/merges/tests/integration/services/merges/tenant-merge-history.integration.spec.js#is the name Platform knows the requester by now, never the id a screen cannot read
`04`must prove Confirmed	Details retain originals, the written survivor and field outcomes with final, discarded and gap-filling values, sources, rules and attributed decisions, together with relationship, login and validation actions. origin: services-crm:docs/milestones/CRM-M4-duplicates-and-merge.md#D-30 no proof recorded yet	policy	service	test services-crm:modules/merges/tests/integration/services/merges/merge-outcome.integration.spec.js#keeps the reviewer’s choice with what it was, who made it, and the record it was taken from
`05`must prove Confirmed	Merge records remain for the workspace lifetime as retained originals and ordinary application operations cannot erase or relocate them. origin: services-crm:docs/merging/decisions.md#D4 (decided 2026-10-11: option 1) no proof recorded yet	invariant	database	test services-crm:modules/merges/tests/integration/db/record-merges.table.integration.spec.js#may not erase a merge, which holds the only copy left of the records it deleted
`06`must prove Confirmed	The product should allow removal of a person's original merge values in response to a privacy deletion request. origin: services-crm:docs/merging/decisions.md#D4 (decided 2026-10-11: option 1) no proof recorded yet	policy	service	unknown FND-CRM-DQ-010
`07`must prove Confirmed	Record readers may inspect successful merged-from history, field outcomes and originals without merge authority; login actions, carried dismissals and checks require merge-read authority. origin: services-crm:docs/milestones/CRM-M6-access-and-audit.md#D-21 no proof recorded yet	permission	api	test services-crm:modules/merges/tests/integration/services/merges/merged-from-history.integration.spec.js#leaves what only merge management reads out of a reader’s details
`08`must prove Confirmed	Merged-from requests reject authority for only the other record type and return not found for an unreachable record or a merge outside its lineage. origin: D-45 (cited in services-crm:docs/merging/api.md#2. Authorization; no milestone record holds it, FND-CRM-DQ-018) no proof recorded yet	permission	api	test services-crm:modules/merges/tests/e2e/merged-from-history.e2e.spec.js#refuses a reader of organizations a contact’s merged-from history
`09`must prove Confirmed	Console Recently Merged and management details require merge-read authority, and record version history provides merge entries linking to their outcomes. origin: services-crm:docs/merging/experience/functional-requirements.md#AUD-2 no proof recorded yet	permission	console	test react-console:acceptance/crm/playwright/journeys/merging/CRM-ACC-0266.spec.ts#CRM-ACC-0266
`10` Confirmed	Workspace exports include merges, absorbed originals and their aliases.	policy	service	observed services-crm:modules/merges/export/merges.dataset.ts:mergesDataset
`11` Confirmed	Merging has no undo operation; repairing a mistake requires survivor edits or record recreation from retained originals, and the console communicates that limit. origin: services-crm:docs/merging/experience/functional-requirements.md#GEN-8	policy	console	documented services-crm:docs/merging/architecture.md#7.4 What can and cannot be undone

Scenarios

Id	Given	When	Then	Provenance
`01`	Two contacts have been merged successfully.	A colleague with record-read authority opens the survivor's merged-from history.	They see merge attribution and absorbed originals without needing merge-management permission.	test services-crm:modules/merges/tests/e2e/merged-from-history.e2e.spec.js#answers the reader the merge’s outcome and the absorbed record as it was
`02`	Several people have requested merges.	An administrator filters history by type, status, author and date.	Entries identify the records and attribution, with details showing retained, moved and discarded information.	test react-console:acceptance/crm/playwright/journeys/merging/CRM-ACC-0266.spec.ts#CRM-ACC-0266

Planning

Inspect merge outcomes and attribution ​

Purpose ​

How It Works ​

Relationships ​