PRML manifest registry

Lock the claim. Then run.

A public, content-addressed index of pre-registered ML evaluation claims. Paste your PRML manifest, get a SHA-256-anchored permalink and a README badge. No account, no server-side state beyond the hash.

◆ Tamper Strip · live
0 / 64 nibbles changed↻ reset

same bytes → same hash, forever. that is the entire spec.

▸ First time? 60-second walkthrough

◆ 1 · What you need

A YAML file with 9 fields. Copy the template below into the form as a starting point, then replace each value with yours.

version: "prml/0.1"
claim_id: "01900000-0000-7000-8000-000000000000"
created_at: "2026-05-17T12:00:00Z"
metric: "accuracy"
comparator: ">="
threshold: 0.85
dataset:
  id: "imagenet-val-2012"
  hash: "e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855"
seed: 42
producer:
  id: "your-org.com"

◆ 2 · What happens when you submit

The server canonicalizes the YAML (PRML §3), computes the SHA-256 of those bytes, stores the manifest publicly, and returns a permalink at /<hash> plus a README badge.

◆ 3 · What to do with the hash

  • Add the README badge to your repo.
  • Cite the permalink in papers and audit reports.
  • Use prml-verify-action in CI to gate future merges.
  • Anyone with any of the four reference implementations can verify it offline.

◆ 4 · What is locked

Any field change after submission produces a different hash. That's the entire mechanism. Pre-registration is the act of submitting before you run the eval — the hash binds the threshold.

Public by design — and once a hash is countersigned by the external timestamp authority and transparency log, those countersignatures cannot be recalled, by you or by us. No personal data in any field: identify as an organisation or pseudonym. privacy · terms

Manifest stays public. Valid PRML gets a "PRML locked" badge; any other YAML is committed as an explicitly labeled raw hash anchor. Spec: spec.falsify.dev/v0.1 · Verify a hash without committing →

Receipts are Ed25519-signed (hash + timestamp, key at /pubkey) and countersigned by an independent RFC 3161 timestamp authority (timestamp.sigstore.dev) since 2026-07-12, so the time claim is verifiable offline against a third party. New commits are also mirrored to Sigstore's public Rekor transparency log (inclusion proof on each permalink). A receipt proves the bar was locked, never the result.

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

◆ Recent submissions

HashTime (UTC)Handle
390e78d9121f8f7a…2026-07-30 12:18:14 UTC
7f6abf985d8d6ee0…2026-07-29 07:40:41 UTC
ceba7a1a2e459458…2026-07-28 18:38:57 UTC@andes-interop-test
7b0943184c4564c7…2026-07-11 21:40:03 UTC@falsify
5a048172ef02e3af…2026-05-16 12:36:09 UTC@onboarding-test
6d85e0c3d3af4467…2026-05-15 19:07:35 UTC@falsify.dev
4b6a9194bb187b88…2026-05-15 19:07:34 UTC@falsify.dev
4f16767c89fbae1b…2026-05-15 18:40:40 UTC@falsify-seed

◆ Related