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-256
af0bfb6d39b17e3ba8520b743043ff3d7cd303a14b02d526d9a5de9ed04b2375Registered2026-08-23T05:43:55.879Z
Independent timestampRFC 3161 · 2026-08-23T05:43:56Z · timestamp.sigstore.dev · token
Transparency logRekor v2 · log2025-1.rekor.sigstore.dev · index 76716892 · inclusion proof
KindPRML manifest — conformed to the published v0.1 schema at commit time
Manifest
version: prml/0.1 claim_id: 01a02d25-9f34-7cf4-9a75-1bdb11ea0da9 created_at: '2026-08-23T05:43:55Z' metric: mastra_eval_verdict metric_args: scorer: location-accuracy gates: [answered-in-english] tracked_thresholds: 1 comparator: '>=' threshold: 0.9 dataset: id: mastra/criteria.json hash: fae800c04e7b9c58522111ce07b85e8154d6ae3d0e15be3c1712bf65d0b25627 seed: 0 producer: id: bridge-test.localraw bytes →
README badge
[](https://registry.falsify.dev/af0bfb6d39b17e3ba8520b743043ff3d7cd303a14b02d526d9a5de9ed04b2375)Verify in CI
- uses: studio-11-co/prml-verify-action@v2
with:
mode: verdict
expected-hash: af0bfb6d39b17e3ba8520b743043ff3d7cd303a14b02d526d9a5de9ed04b2375github.com/studio-11-co/prml-verify-action →Verify this hash yourself
Paste your manifest YAML. The canonical hash must match af0bfb6d39b1…. 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/af0bfb6d39b17e3ba8520b743043ff3d7cd303a14b02d526d9a5de9ed04b2375.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 af0bfb6d39b17e3ba8520b743043ff3d7cd303a14b02d526d9a5de9ed04b2375 \
-in af0bfb6d39b17e3ba8520b743043ff3d7cd303a14b02d526d9a5de9ed04b2375.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. Where a "Transparency log" row is present, the hash is additionally mirrored to the public Sigstore Rekor log with a verifiable inclusion proof.
- 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.
- Limitations: the registry itself is a signed key-value store, not an append-only log — per-record non-equivocation comes from the Rekor entry, and records committed before full-manifest storage (2026-07-11) carry their RFC 3161 token only. No long-term storage guarantee: mirror your hashes in your own infrastructure.
PRML v0.2 is a frozen RFC (comment window closed 2026-05-22) — spec.falsify.dev/v0.2-rfc. Editor: spec.falsify.dev/editor.