Can you check a stranger without asking anyone?

A gate is a decision at the door. Someone arrives, presents something, and the operator accepts or refuses. What matters is where the evidence for that decision has to live.

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

So the visitor is not what gets assessed. The row about the visitor is what gets assessed, and the row belongs to someone else. If that party is down, stale, or no longer willing to return the row, the gate has no second source. The operator still holds a policy, and they also hold a dependency they do not control.

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

The question at the door 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.

That computation still needs a clock both sides can read without calling each other. What that clock is, is How do you prove when the work happened?

What has changed is the supply line. Before, the operator held a policy and a live dependency on someone else's cooperation. Now they hold the policy alone, and the facts the policy reads arrive with the visitor. Whether the fact is enough is Why can saying no be cheap when saying yes cannot?