An administrator places the e-mail blocker first in duplicate configuration. A coordinator encounters its refusal while creating a look-alike contact. An administrator with override authority then provides a reason and creates the distinct person. The exception receives its own retained record, and the resulting pair remains reviewable. Applying later configuration to existing records requires an API re-check; the proposed console management flow remains incomplete.
The Formal Contract
The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.
Goal
Prevent ordinary duplicate creation while retaining authorized, explained exceptions.
End-to-end policy: required: Configuration, draft warnings and the exception dialog involve browser permissions and service authorization; re-check management currently requires API evidence.