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-256148fc494feb68eb2991c9aee28ee762059aa6f6b7206035e0e863b0ddd8f9e96

Registered2026-05-07T09:05:00.389Z

Independent timestampRFC 3161 · 2026-07-11T22:19:05Z · 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@smoke-test

Manifest preview

version: prml/0.1
metric: accuracy
threshold: 0.85
dataset_split: imagenet-val
model_version: stub-v1
claim: smoke test
submitter: studio-11
timestamp: 2026-05-07T12:00:00Z

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](https://registry.falsify.dev/badge/148fc494feb68eb2991c9aee28ee762059aa6f6b7206035e0e863b0ddd8f9e96.svg)](https://registry.falsify.dev/148fc494feb68eb2991c9aee28ee762059aa6f6b7206035e0e863b0ddd8f9e96)

Verify in CI

- uses: studio-11-co/prml-verify-action@v2
  with:
    mode: verdict
    expected-hash: 148fc494feb68eb2991c9aee28ee762059aa6f6b7206035e0e863b0ddd8f9e96

github.com/studio-11-co/prml-verify-action →

share on x →

Verify this hash yourself

Paste your manifest YAML. The canonical hash must match 148fc494feb6…. 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/148fc494feb68eb2991c9aee28ee762059aa6f6b7206035e0e863b0ddd8f9e96.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 148fc494feb68eb2991c9aee28ee762059aa6f6b7206035e0e863b0ddd8f9e96 \
  -in 148fc494feb6.tsr -CAfile tsa-1.pem -untrusted tsa-0.pem

Expected output: Verification: OK.

What this receipt proves — and what it does not

Proves: these manifest bytes hashed to this SHA-256, and the registry attests (Ed25519 signature over hash + timestamp, key at /pubkey) that it saw the hash at the recorded time.
Timestamp: where an RFC 3161 token is present (the "Independent timestamp" row above), the time claim is countersigned by a public timestamp authority and verifiable offline; backdating it would require compromising that authority, not just this registry. Records without a token rest on the registry's clock alone until anchored. Transparency-log (Rekor) inclusion is still planned — see registry limitations.
Does not prove: the claimed result. A PRML receipt proves the bar was locked before the run — never that the result is good.
The signature covers hash + timestamp only, not the submitted handle. There is no key-rotation story yet; the current key id is served at /pubkey.

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