Public registry

Recent commits.

Every PRML manifest committed to registry.falsify.dev, in the order it was registered. Content-addressed, immutable, publicly verifiable against any of the four reference implementations. Commits are grouped by who made them: independent submissions first, then Falsify's own examples and test submissions. Both are real commits carrying real countersignatures, and both stay on the board.

6commits to date

Examples & test submissions

Reference submissions used for interoperability, integration and documentation testing.

#dateproducer.idclaimhash
0012026-07-28andes-interop-test>= 1 on andes-synthetic-interop-fixture-v1ceba7a1a2e45
0022026-07-29andes-interop-demo.falsify>= 0.78 on synth-credit-tabular-v17f6abf985d8d
0032026-08-23docs-check.local>= 0.7 on bridge-doc-check6385794f9f90
0042026-08-23bridge-test.local>= 0.9 on mastra/criteria.json1e426a9a6eab
0052026-08-23bridge-test.local>= 0.9 on mastra/criteria.jsonaf0bfb6d39b1
0062026-08-25worked-example.falsify>= 0.8 on uci-statlog-german-credit132437f156e8

How to commit a manifest

Paste your PRML manifest at registry.falsify.dev. No account required. Once a manifest is committed, the hash binds it to the canonical bytes you submitted, and the external countersignatures on that hash cannot be recalled.

Slot order is determined by registry commit timestamp. Producer identity is taken from the manifest's producer.id field as published — we do not verify domain ownership. If your organization's identifier has been used in a commit without authorization, email hello@falsify.dev with subject [TAKEDOWN] and we will redact within 5 working days.