Manifest receipt

Locked & verifiable.

A pre-registered claim, anchored to a SHA-256 hash before the run. Anyone can re-derive it from the canonical bytes below.

SHA-2569d028ef6fc3af63277921ceaab146359589298e734b146c57a4158d72676f39c
Registered2026-05-15T18:36:42.165Z
Independent timestampRFC 3161 · 2026-07-11T22:19:26Z · timestamp.sigstore.dev (anchored after commit; earlier existence rests on the registry signature alone) · token
Transparency lognot yet in a public log (record predates full-manifest storage; RFC 3161 token only)
Kindcommitted before 2026-07-11 — not validated at commit time; re-verify offline with a reference implementation
Submitted by@falsify-seed
Manifest preview
version: "prml/0.1"
claim_id: "01897d80-0000-7a01-8000-00000000004a"
created_at: "2023-08-14T10:00:00Z"
metric: "accuracy"
metric_args:
  shots: 5
comparator: ">="
threshold: 0.864
dataset:
  id: "mmlu-test"
  hash: "c1f9b6d6a3e7d4b2f0a18c5e7d2b9f4a6c8e1d3b5a7c9e2f4d6b8a0c2e4f6a8b"
  uri: "https://huggingface.co/datasets/cais/mmlu"
model:
  id: "gpt-4-0314"
seed: 0
producer:
  id: "falsify.dev"
notes: "Retroactive demo lock — original claim is OpenAI's, not falsify.dev's."
Note (2026-07-11): records committed before this date stored only a 500-byte preview, so this page cannot prove the full manifest. Re-verify offline against the original file.
README badge
PRML locked[![PRML locked](https://registry.falsify.dev/badge/9d028ef6fc3af63277921ceaab146359589298e734b146c57a4158d72676f39c.svg)](https://registry.falsify.dev/9d028ef6fc3af63277921ceaab146359589298e734b146c57a4158d72676f39c)
Verify in CI
- uses: studio-11-co/prml-verify-action@v2 with: mode: verdict expected-hash: 9d028ef6fc3af63277921ceaab146359589298e734b146c57a4158d72676f39cgithub.com/studio-11-co/prml-verify-action →

share on x →

Verify this hash yourself

Paste your manifest YAML. The canonical hash must match 9d028ef6fc3a…. This runs the registry's own canonicalization module (canonical.js) in your browser; for verification that does not trust this registry at all, use any of the four reference implementations offline.

Verify the independent timestamp (RFC 3161, offline)

The token countersigns this manifest hash with the timestamp authority's key, so the time claim no longer rests on this registry. Verify with OpenSSL 3 (LibreSSL, the macOS default, cannot check the ESS extension):

curl -sO https://registry.falsify.dev/9d028ef6fc3af63277921ceaab146359589298e734b146c57a4158d72676f39c.tsr
curl -s https://timestamp.sigstore.dev/api/v1/timestamp/certchain -o chain.pem
awk 'split_after==1{n++;split_after=0} /END CERTIFICATE/{split_after=1} {print > ("tsa-" n ".pem")}' n=0 chain.pem
openssl ts -verify -digest 9d028ef6fc3af63277921ceaab146359589298e734b146c57a4158d72676f39c \
  -in 9d028ef6fc3a.tsr -CAfile tsa-1.pem -untrusted tsa-0.pem

Expected output: Verification: OK.

What this receipt proves — and what it does not

PRML v0.2 is a frozen RFC (comment window closed 2026-05-22) — spec.falsify.dev/v0.2-rfc. Editor: spec.falsify.dev/editor.