=== VERIFICATION TRANSCRIPT — 2026-08-25T08:25:58Z ===

$ python3 falsify_prml.py verify manifest.yaml
OK  hash verified  sha256:132437f156e81d7c16822847a3c101b146b2a846828f0ddeb933efcf464667f5
(no --observed value given; predicate not evaluated)

$ shasum -a 256 german.data
b21f3d81db8071257d5ff1deaeba1fd4303b62712e6fcc9715c7a86202cb5871  german.data

$ curl -s https://registry.falsify.dev/132437f156e81d7c16822847a3c101b146b2a846828f0ddeb933efcf464667f5.yaml | shasum -a 256
afaceab9e03038c5213dfcc76751004d7806a242101f62612c96883e6c46a3fe  -
  (local manifest.yaml: afaceab9e03038c5213dfcc76751004d7806a242101f62612c96883e6c46a3fe)

$ openssl ts -verify -digest 132437f156e81d7c16822847a3c101b146b2a846828f0ddeb933efcf464667f5 -in receipt.tsr -CAfile chain.pem
Verification: OK

$ openssl ts -verify -digest <one character changed> -in receipt.tsr -CAfile chain.pem
Verification: FAILED
  (negative control: the check discriminates)

$ python3 run_eval.py
  impact_ratio=0.857919
  selection_female=0.677083
  selection_male=0.789216
  n_test=300
  n_female=96
  n_male=204
  verdict=PASS

--- environment note ---
The openssl lines above were run with OpenSSL 3.x.

On macOS, /usr/bin/openssl is LibreSSL, not OpenSSL. It verifies this receipt
fine, but it cannot verify RFC 3161 tokens that use ESSCertIDv2 (SHA-256) in the
signing-certificate attribute — it reports "ess signing certificate error" and
prints Verification: FAILED. That is the tool refusing to read the token, not a
bad token. Qualified EU timestamp authorities emit exactly that shape, so if you
ever check a qualified token, use OpenSSL 3.x (brew install openssl@3).

--- sealed commits (registry, since 3 September 2026) ---
A producer that cannot publish its criteria can commit the same manifest
sealed: the registry validates, hashes, signs and anchors it, but serves no
text. The receipt then proves that bytes with this hash existed at the
recorded time; a party shown the manifest privately verifies it against the
hash exactly as above. POST /<hash>/reveal publishes the text later, and is
accepted only if the bytes re-derive the hash. Nothing else can unseal it.