Can you check a stranger without asking anyone?

The evidence is in the file, not in a lookup.

You have a file from someone you have never met. The question is whether you can tell what it claims without calling them, and without calling an office that listed them.

Almost every check in use today works by lookup. The visitor presents an identifier. The identifier carries almost nothing of its own. It is a pointer. The answer sits at the other end of it: a directory, a registry, a provider. You cannot decide from the thing in your hand. You have to reach someone else's record, and that record has to be reachable, current, and honest at the moment you ask.

So the visitor is not what gets assessed. The row about the visitor is. The row belongs to someone else. If that party is down, stale, or no longer willing to return the row, you have no second source. You still hold a policy. You also hold a dependency you do not control. Issued, listed, or made? is that office.

There is another place the evidence can live. The visitor can present an object that carries its own production: work that was done, bound to a key the holder controls, and placed in a public order. You examine the object. The arithmetic runs on your machine. The answer is derived from the file, not retrieved from an office.

The question changes with that move. Lookup asks whether this person is listed in someone else's database. The object asks whether this file cost what it claims to cost. One is a query. The other is a computation over the thing in front of you.

The when in that computation is the public sequence, already named. You do not call the sequence either. How do you prove when the work happened? Both sides can read it without calling each other.

What has changed is the supply line. Before, you held a policy and a live dependency on someone else's cooperation. Now you hold the policy alone, and the facts the policy reads arrive with the visitor. Whether the fact is enough is Why is the check always cheaper than the making?