Dismiss false matches and reopen review

Purpose

Reviewers can record that records describe different identities and revisit that decision when needed.

How It Works

The reviewer marks a pair or a complete group as Not a Duplicate. Rhythm retains the author, time, optional note and evidence behind that decision. A group dismissal settles all its open pairs together. Another reviewer who repeats the dismissal receives success and attribution rather than replacing the earlier decision. Restoring a pair removes its dismissal details and makes it open again. Undoing a group dismissal restores the pairs changed by that group decision, preserving separate earlier dismissals. Ordinary name corrections do not reopen a settled pair. New strong identity evidence can reopen it and explain why. Read-only reviewers see suggestions without decision controls. Removing a member of a group in the console dismisses its connections to the other displayed records.

Relationships

Group review provides the decision surface. Detection compares later evidence with the dismissal fingerprint. Merge execution carries applicable outside-pair dismissals to the survivor.

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: Dismissals preserve review decisions until explicit restoration or new strong evidence.Concurrent repeated dismissals retain one attributed decision.Mistaken decisions can be restored immediately or from dismissed work.
Surfaces: consoleapi
Intent sources: services-crm:docs/milestones/CRM-M4-duplicates-and-merge.md#D-34services-crm:docs/merging/experience/functional-requirements.md#DIS-1 to DIS-7 (package approved by Andrew 2026-10-13)

Controls

23 controls apply, from the corpus control catalogue.

TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-AZ-006 TC-CRY-004 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-PI-002 TC-PI-003 TC-PI-005 TC-PRV-001 TC-PRV-002 TC-TEN-001 TC-TEN-002 TC-TEN-003

Permissions

Key	Checked at	Scope
`crm.duplicates.review`	api	tenant

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	Pair dismissal retains the reviewer, time, optional trimmed note up to 1,000 characters and current strong evidence, moving the pair into dismissed grouping. origin: services-crm:docs/merging/experience/functional-requirements.md#DIS-1 no proof recorded yet	lifecycle	api, service	test services-crm:modules/duplicates/tests/e2e/duplicates.e2e.spec.js#records the evidence the dismissal was made against, which a later score is compared with
`02`must prove Confirmed	Repeating a pair or group dismissal succeeds without changing it and returns the earlier author as visibility permits, time and note. origin: services-crm:docs/milestones/CRM-M4-duplicates-and-merge.md#D-34 no proof recorded yet	policy	service	test services-crm:modules/duplicates/tests/integration/services/persistence/duplicate-candidates.integration.spec.js#answers the second reviewer the EARLIER dismissal: its who, its name as visibility permits, its when and its note
`03`must prove Confirmed	Group dismissal atomically settles every open pair using one author, time and note with each pair's evidence, then returns the dismissed group's identity. origin: services-crm:docs/merging/experience/functional-requirements.md#DIS-2 no proof recorded yet	lifecycle	service	test services-crm:modules/duplicates/tests/integration/services/persistence/duplicate-candidates.integration.spec.js#leaves no pair of the group dismissed, a group being decided about whole or not at all
`04`must prove Confirmed	Undoing a group dismissal reopens only pairs changed by that decision, preserves independent dismissals and rejects a group with nothing to restore. origin: services-crm:docs/merging/experience/functional-requirements.md#DIS-3 no proof recorded yet	lifecycle	service	test services-crm:modules/duplicates/tests/integration/services/persistence/duplicate-candidates.integration.spec.js#leaves the pair somebody dismissed on its own dismissed, that being a decision of its own
`05`must prove Confirmed	Pair restoration clears author, time, note and dismissal evidence while retaining current score and reasons; no earlier dismissal history remains. origin: services-crm:docs/merging/experience/functional-requirements.md#DIS-5 no proof recorded yet	lifecycle	service	test services-crm:modules/duplicates/tests/integration/services/persistence/duplicate-candidates.integration.spec.js#takes the whole dismissal off: who, when, why and on what evidence
`06`must prove Confirmed	Later record edits preserve dismissal unless new shared e-mail, phone, origin, birth-date or street evidence appears, or organization domain, phone or address evidence appears; reopening explains the new evidence, and name corrections alone do not reopen it. origin: services-crm:docs/merging/experience/functional-requirements.md#DIS-7 no proof recorded yet	lifecycle	service	test services-crm:modules/duplicates/tests/unit/services/matching/fingerprint.spec.js#leaves a pair dismissed when a name typo is fixed and nothing strong changes
`07` Confirmed	Changing the scoring version preserves dismissals while open pairs receive updated scores. origin: services-crm:docs/merging/README.md#Status (architecture and plan approved by Andrew 2026-10-11)	policy	service	documented services-crm:docs/merging/duplicate-detection.md#8. Dismiss, confirm, reconsider
`08` Confirmed	A dismissal applies only to its two records and does not exclude either from comparisons with others. origin: services-crm:docs/merging/experience/functional-requirements.md#DIS-6	policy	service	inferred services-crm:modules/duplicates/services/persistence/duplicate-candidates.ts
`09`must prove Confirmed	Dismissal and restoration require duplicate-review authority, with readers refused by the API and decision controls hidden in the console. origin: services-crm:docs/merging/architecture.md#9. Security and tenant isolation no proof recorded yet	permission	api, console	test services-crm:modules/duplicates/tests/e2e/duplicates.e2e.spec.js#answers 403 to that reader dismissing a pair, which is a decision and not a read
`10`must prove Confirmed	Notes exceeding 1,000 characters are rejected, and unavailable workspace pairs or groups return not found. no proof recorded yet	validation	api	test services-crm:modules/duplicates/tests/e2e/duplicates.e2e.spec.js#refuses a dismissal note longer than a note may be (400)
`11`must prove Confirmed	Removing a record from a displayed group dismisses its pairs with the other members without dismissing the remaining group. origin: services-crm:docs/merging/experience/functional-requirements.md#REV-5 no proof recorded yet	policy	console	test react-console:acceptance/crm/playwright/journeys/merging/CRM-ACC-0234.spec.ts#CRM-ACC-0234

Scenarios

Id	Given	When	Then	Provenance
`01`	A reviewer dismisses a pair and records a note.	The contacts later acquire a new shared mobile number.	The pair reopens with a new-evidence explanation and the dismissal note is cleared.	test react-console:acceptance/crm/playwright/journeys/merging/CRM-ACC-0236.spec.ts#CRM-ACC-0236
`02`	Two reviewers submit dismissal for the same group in sequence.	The second submission reaches the service.	It succeeds without changes and shows the first author and note.	test services-crm:modules/duplicates/tests/e2e/duplicate-groups.e2e.spec.js#answers a second dismissal of the dismissed group 200, saying it was already dismissed (D-34)

Planning

Dismiss false matches and reopen review ​

Purpose ​

How It Works ​

Relationships ​