The Data Quality overview summarizes each record type. It distinguishes groups, records and pair decisions so staff can understand what each count represents. Confidence counts follow the strongest pair in a group. Zero activity remains visible as a zero-valued section. Counts stop at a stated ceiling and are displayed as a floor once capped. The summary also identifies a running re-check and recent successful merges. Reviewers follow count links into the appropriate queue. Duplicate-read authority controls both page and API access. The attention declaration is held and currently not delivered. The product should complete the object registration before relying on responsibility-based notifications.
Group and candidate storage supply the counts. Re-checks supply running status and merge history supplies recent success totals. Platform owns attention delivery.
The Formal Contract
The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.
Outcomes
The overview makes waiting duplicate work understandable.Capped large totals are identified as lower bounds.
7 rules, 5 to be proved before approval. A rule's product intent is derived from its origin: 7 confirmed by a product decision, the rest inheriting this capability's confirmed.
Id
Rule
Kind
Enforced at
Provenance
01must prove
Confirmed
For each type the overview reports open groups by confidence, their records, open/dismissed/confirmed pairs, latest group detection, active re-check status and successful merges within 30 days.
The overview links type counts to filtered review queues, renders capped totals as 10,000+ and uses counts consistent with open, dismissed and confirmed work.
The product should notify duplicate-management responsibility of open groups and resolve that attention as groups close; the declaration is currently held and sends no notifications.