Match Review, at /admin/catalog/matching, is a super-admin surface where a human decides how one product's events map onto another's. A "match" is a clearinghouse registry entry that connects a producer event (producerProduct · producerEventType) to a consumer event (consumerProduct · consumerEventType). When the matchmaker cannot resolve a candidate on its own it raises an escalation, which lands in this queue. The list shows the Producer, Consumer, a reason such as "Authorized-use missing" or "Consume shape unresolved", a numeric confidence, and a status. Filter chips switch the view between open, resolved, and all. Opening an escalation reveals the editable Mapping definition JSON and, for matches touching sensitive fields, an "Authorized use" table mapping each consumer field to its authorized use. Operators Accept a match (a two-step affirmation is required when sensitive fields are present) or Reject it with a written reason; a resolved escalation becomes read-only. A separate "New manual mapping" page installs a mapping directly as active without LLM evaluation.
suite
Match Review
The operator queue for reviewing proposed producer-to-consumer event matches that the clearinghouse could not auto-resolve.
Technical section
Data model, API, and internals — visible to developers.
