Audit repeat creation beyond duplicate-warning telemetry

A duplicate-warning stream measures encounters with an instrumented guard, not every repeated creation. When an interactive path checks for existing work but an API path creates records directly, API repeats can produce distinct parent records without any warning or override event. Audit creation receipts across entry points, grouping by tenant and exact business reference while counting distinct parent IDs. Then separate contact changes and legitimate replacements from redundant requests. Matching masked phone suffixes is supporting evidence only; it cannot establish identical recipients or payloads.

Applies when: interactive and API creation paths have different duplicate checks or telemetry. Keywords: API duplicate creation warning telemetry parent identity replay contact replacement