Verification

Verification answers a narrow question precisely. The value is in knowing which question.

Six things that are not the same

You established	It means	It does not mean
Transport success	A 200 came back.	Anything at all about the content.
Artifact integrity	The bytes match a published digest.	That the laboratory published them — only that they match the digest you were also given.
Cryptographic authenticity	A signature ties bytes to a key.	Anything scientific. Not available here — no signing exists yet, and this page will say so until it does.
Reproducibility	Re-running the code gave the same output.	That the finding is true. It can faithfully reproduce a broken measurement — the fixture on this site does exactly that.
Scientific qualification	The record passed the published rules for its status.	That anyone independent agrees.
Independent replication	Different people, implementation and data met criteria fixed in advance.	That it generalises beyond the tested scope.

A site that renders all six as one green tick is making an argument it has not earned.

Verify a record digest

Each claim version carries identity.digest, taken over a canonical serialization of record with its own digest field removed. You can recompute it from the response alone:

curl -s https://tiffany.systems/demo/bundles/demo-0001-v2.json -o bundle.json
node tools/verify.mjs bundle.json     # from the site repository, ~60 lines, no dependencies

The canonicalization is published in full so you can re-implement it without our code: keys sorted by UTF-16 code unit, no insignificant whitespace, array order preserved, non-integer and non-finite numbers rejected rather than coerced, SHA-256 over the UTF-8 bytes. An identity scheme you cannot re-derive is not verifiable.

Verify an artifact

curl -sO https://tiffany.systems/demo/artifacts/demo-a-input.csv
shasum -a 256 demo-a-input.csv
# compare with the sha256 in the record's artifacts[] or the bundle's manifest[]

Verify the whole site at once

curl -s https://tiffany.systems/build-manifest.txt

SHA-256 of every file the build wrote, except itself — a manifest cannot contain its own digest. A build test asserts nothing is served from this origin without appearing there, which is how a shipped-but-unmanifested asset gets caught.

Check current versus exact state

# what the laboratory asserts today
curl -s https://tiffany.systems/api/demo/claims/demo-0001.json | jq '.current_version'

# what the version you cited says, which never changes
curl -s https://tiffany.systems/api/demo/claims/demo-0001/v2.json | jq '.record.lifecycle, .record.superseded_by'

Both are true at once, and a client holding a stored record should re-check the identity document before presenting it as current.

Signatures

Not available. There is no signing key and no transparency log. Both were designed and deferred: with a single publisher and no external replications, signatures would attest to one operator signing their own work, adding a compromise and rotation surface without adding independent assurance. The digest lock over published versions detects the tampering a log would detect at this scale.

The activation conditions are recorded in the deferred ledger. When one is met, this page changes.

PreviousPlayground

NextMachine clients