Rhythm 2.0 Specifications

Appearance

WF-CRM-DQ-001Detect duplicates after a committed change

Markdown

WF-CRM-DQ-001

Detect duplicates after a committed change

Markdown
  • DocumentDraft
  • ImplementationObserved

Planning

Implements
CAP-CRM-DQ-001, CAP-CRM-DQ-002, CAP-CRM-DQ-003, CAP-CRM-DQ-007, CAP-CRM-DQ-008, CAP-CRM-DQ-011

KindWorkflowProduct areaCRMModuleDuplicate Review and Record MergingRevision1

Read atservices-crm a8d1364f

Detect Duplicates After A Committed Change ​

What It Does ​

Background comparison follows a successful save rather than extending its transaction. It replaces comparison keys, recalculates eligible evidence and keeps affected review groups aligned with the pair writes.

The Flow ​

When Something Fails ​

Handler failure returns the batch for another delivery. Key refresh occurs before the pair-and-group transaction, so a failure does not prove that every pass write is undone. Exhausted events leave stale evidence until operator recovery or another change. Attention publication is currently held.

Open Design Questions ​

Import-marked changes have no completion caller. Review-versus-detection races and the full pass transaction boundary need stronger implementation and proof before they are treated as guarantees.

Controls

26 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-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-002 TC-PI-003 TC-PI-004 TC-PI-005 TC-PRV-001 TC-PRV-002 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