03Matching records

Matching records.

A similarity score of 0.93 does not say which side of “the same person” it is on, and a merge cannot be undone quietly. A person reads the fields that decide it and answers the question the pipeline actually has: same, or not.

Reads what decides itThe field that breaks the match, not the fields that agree.
Same, or notA decision, where fuzzy matching only gives you a score.
Priced by the mistakeMerging two people’s records costs more than a duplicate row.
Only what you sendThe records you put in the question, and nothing from your database.

Your agent sends

Record ASam Okafor · sam.okafor@mail.com · born 1991

Record BSamuel Okafor · sam.okafor@mail.com · born 1964

Are these the same person?

Quorum’s analysis

What happened

The agent’s matcher scored 0.93Same name root, same email address.

Amara read both recordsNo: born 27 years apart. 0.926.

Joel was asked independentlyNo. Together, 0.990.

No. Two people.

A shared family email, not one customer. The records stay apart, and neither sees the other’s history.

How it works

Step by step.

Send only the pairs your matcher could not settle. Quorum takes the uncertain middle, not the whole table.

01SendThe records in question.

02ReadSomeone proven at matching.

03WeighA second look if one is not enough.

04AnswerSame or not, with its confidence.

Real-world example

A father and son, one inbox.

A customer-data agent deduplicates accounts. Two records share an email address and a surname, and its matcher is 0.93 sure they are one person. Merged, a son would see his father’s orders and addresses. A person notices the birth years, and the merge does not happen.

Matcher: same person, 0.93Not merged

Answer: two people, 0.990Kept apart

Customer dataDeduplicationSupplier records

For crypto agents

Where this saves a transaction.

An on-chain payment cannot be taken back, so the moment before the agent signs is the moment to ask.

Payments agentThe same bill, sent twice?A contractor’s invoice was paid last week. Now one arrives with a new layout, a new reference and the word “balance”. A new bill, or the same one again? Paying twice in USDC can’t be reversed.

Treasury agentThe same counterparty?“Northwind Security” has been paid for a year. “NW Sec Audits LLC” now sends a bill from a new wallet, citing the same audit. The same firm, or someone borrowing its name? A person reads both records and decides.

The agent holds the transaction, not the market. It asks before it signs and waits about six seconds for the answer. Set deadline_ms to the window you actually have: if nobody answers in time you are refunded, and the agent takes its safe path, which is not to sign.