Ambiguous merge
A cluster of records that the matching engine flagged as "probably the same entity, but confidence is in the middle band — please review."
When entity resolution produces a cluster where all pair scores cleared the auto-merge threshold, the cluster gets merged silently. When at least one pair score fell into the configurable "ambiguous" band — say, between 0.7 and 0.85 — the cluster lands in the review queue instead of getting merged.
Ambiguous merges are the right place for stewards to spend their attention. The engine is saying "I'm not certain, and the downside of a wrong merge here is high — you decide."
Approve / split / merge actions on review-queue items are captured in the audit log with the steward's user ID, so policy decisions on edge cases become part of the org's institutional memory.