Verify normal, never accuse.

The principle

We do not hunt for wrongdoing. We know what normal looks like, we verify it, and we give our attention only to what does not verify.

Hunting for what is wrong finds whatever the hunter expects: a place, a name, a type of person. Verifying normal finds only what fails to check out, and it explains itself in evidence. It is calmer, fairer and faster, and it holds up in front of a client, an insurer, a lawyer or a court. A verifier that hunts is an accuser, and an accuser’s signature is worth little. A verifier that confirms normal and names only what failed to verify is the source of truth.

The process, every time

1. Know normal before you look.Normal is measured, not assumed, and it is specific: the platform’s usual account-day, the usual gap from deposit to shipment request, the usual cards per account; the account’s own history; the issuer’s footprint and how a real holder’s card behaves; whether the door is residential or commercial and deliverable; the carrier’s authority, insurance and the contact that matches the public record.
2. Write the normal story.One or two sentences of what this transaction would look like if it were exactly what it appears to be. An account deposits with its own card, at its usual pace, and ships to its own door.
3. Verify each part of the story against evidence.Every part gets one of three marks, with its source. Verified: the evidence confirms it. Not verified: we cannot confirm it yet, and draw no conclusion. Contradicted: the evidence says otherwise.
4. Try to make it normal first.Before anything is escalated, give the innocent explanation its strongest form and test it. Only what normal cannot explain moves forward.
5. Decide under the client’s rules.Everything verified is GO. Parts not verified is ESCALATE, naming the exact gap and the one piece of evidence that would close it. A rule contradicted is HOLD, citing the rule.
6. Ask for verification, never accuse.Every request is phrased as what would verify it: the issuer’s confirmation of the cardholder name, the billing street, the account-created time. Never a demand for proof of innocence.
7. Record what was verified, not what was suspected.The record lists each part of the normal story, its mark and its source. Suspicion is not a record entry.
8. Update normal.Every outcome, released and delivered without dispute, refunded, charged back, confirmed, moves the baselines. Normal is re-measured regularly, per client.

The three words

• GO everything verified
• HOLD a rule contradicted, cited
• ESCALATE a gap named, a reviewer signs

The rules are the client’s, written with the desk and owned by the client. Every threshold lives in the client’s own rules file, never in our code, and changing a limit is a new version of that file. Any hold fired is a HOLD. Otherwise any escalation fired, or a required check that could not be run, is an ESCALATE. Otherwise GO. A missing input never passes; it is reported as not tested. An ESCALATE stays open until a named reviewer signs it GO or HOLD; software never signs.

What a determination is made of

• The determination. May this order, load or payment be released under the client’s written rules? Answered GO, HOLD or ESCALATE with the rules cited, by the rules themselves. It is deterministic: the same inputs under the same rules give the same answer, every time.
• The reads. A recipient read asks whether the address, the phone, the email and the names agree with each other and with the record. A pattern read asks what a set of payments looks like and whether the deposits will stand, and answers with a percentage against a named pattern and the evidence that would settle it. Reads explain; they never decide. A rule may take a read as one of its inputs. Where a model assists a read, it is advisory only.
• Custody and carriers. What has actually left and what is held, from the carrier’s own scans and the floor’s confirmation. A label is not a shipment; only a carrier scan means it left.

None of the three says anything about a person. Every line is about an address, a number, a domain, a set of payments, or a parcel.

Words we use, words we don’t

What the desk never does

• Decide on a person. Rules are written as the edges of normal: orders per day, value per day, cards per account, deposits against history. A rule fires when a transaction leaves normal, never because of who or where. A rule that would hold an order because of its neighbourhood is a rule we will not write.
• Own, hold, broker or lend. No inventory, no funds, no position, no fee from the other side of a trade. Custody is arranged through facilities that are disclosed on the first page of every record.
• Contact the client’s customer. Every request for verification goes through the client, phrased as what would verify it.
• Earn from a hold. We are paid per order reviewed, never per order released, so a hold earns us nothing and costs us nothing.
• Sign by software. A named reviewer signs every escalation. Dual control is never automated.

How the method changes

A weight, a mapping or a rule template changes only by one change that edits this page, the code and the tests together. Every record pins the version of the engine, the pattern read and the client’s rules it was decided under, so an old record is never re-read under new weights without saying so. If this page and the code ever disagree, the code is wrong and the tests must catch it.

Where it applies

The same eight steps run on a consumer order before the label prints, on a carrier at a dock before the pickup number is released, on a payment instruction before it changes, on a consignee before controlled equipment ships, on a count on a floor and on a supplier before the first wire. The desk is at BSJ Ventures. Inspection, procurement and custody are performed by Brich House, a BSJ Ventures company, under the same record.