A reviewer submits two records of the same type through the API. Both must exist in the current workspace and be different records. The service records a manual confirmation at full score. The reason retains the reviewer and optional note. If a pair already exists, confirmation changes that pair in place. It replaces computed evidence and overrules a dismissal. Confirmed pairs leave ordinary groups. Subsequent detection can change their score but retains the manual origin and confirmed decision. Duplicate-review permission is required. The product should connect the planned console controls so reviewers without merge authority can make this assertion.
Detection supplies computed suggestions, while manual confirmation supplies a human decision. Merge planning remains a separate action requiring additional authority.
The Formal Contract
The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.
Outcomes
Manual confirmation covers known shared identities missed by detection.The product should let nonmerging reviewers hand confirmed duplicates to administrators.
6 rules, 5 to be proved before approval. A rule's product intent is derived from its origin: 6 confirmed by a product decision, the rest inheriting this capability's confirmed.
Id
Rule
Kind
Enforced at
Provenance
01must prove
Confirmed
Manual confirmation stores a confirmed pair at score 100 with manual origin and one reason identifying the reviewer and note.