What Travels in the Exchange, and What the Verifier Checks | Geometry of Trust | Protocol - Lesson 4

The last talk walked through the shape of the exchange protocol — five steps, two messages, nine verification checks on each side. This talk zooms in on the payload itself. When two agents exchange messages, what actually crosses the wire? And when the verifier takes the payload apart, what does each piece prove?

Those two questions are tightly coupled. Every field in the attestation corresponds to a specific check the verifier runs. Every check depends on a specific field being present. The attestation carries nothing that doesn't get checked, and the verifier can't check anything that isn't carried. Laying them side by side is the clearest way to see why the protocol is the specific shape it is.

The attestation carries seven pieces: probe readings, causal scores, geometry hash, model hash, chain, domain scope, and signature. The verifier runs a specific check against each. Signature proves origin. Geometry hash proves ruler identity. Model hash proves model identity. Probe readings get checked against drift threshold. Causal scores get checked for mechanism realness. Chain gets walked link by link. Domain scope gets matched against the registry. Timestamp in the envelope gets checked for freshness.

And the move at the heart of the whole protocol: every value in the attestation can be independently reproduced. Give a regulator the same model, same probes, same input — they compute Φ themselves, run the probes themselves, get the same readings. Bitwise identical means the attestation is truthful. That's what makes attestations evidence rather than testimony.