Your browser parsed the file, re-derived the exact bytes the signature covers — RFC 8785 canonical JSON, object keys sorted, every float already rounded to six decimal places when the passport was written — and checked an Ed25519 signature over those bytes against the one public key this build trusts. Then it compared the expiry date against your own clock.
The canonical form is computed from the parsed document, not from the file’s text. That is why reindenting it, reordering its keys or renaming it changes nothing, and why one digit of one number changes everything.
Nothing was uploaded, and there is no server behind this page to upload to — the site is a static export. The exit code beside the verdict is the number verify_passport.py returns for the same file; npm run check:samples drops every sample through both and is what keeps them agreeing.
Evidence Passport