Playground · In-browser · No server roundtrip

Edit a manifest. Watch the hash update in real time.

Edit the YAML on the left. The right panel shows the canonical bytes (per PRML v0.1 §4) and the SHA-256 in-browser. When you're ready, copy the manifest to a file or anchor the hash publicly at registry.falsify.dev. Examples below load common patterns.

minimal accuracy RLHF win-rate streaming Elo (v0.2) revoked (v0.2)

manifest.yaml — edit me

YAML · auto-canonicalises on every keystroke ready

canonical bytes · SHA-256

(loading…)

UTF-8 · LF endings · sorted keys · one trailing newline 0 bytes

sha-256

(computing…)

Permalink —

README badge (Markdown) —

CLI verify command —

Pure browser computation. The SHA-256 is computed via the Web Crypto API (crypto.subtle.digest) on your device. Canonicalisation here uses js-yaml's deterministic emit (sorted keys, block style, LF endings, single trailing newline, UTF-8) — close to the v0.1 reference but may differ in edge cases (string quoting, float formatting). For audit-grade hashes, run falsify lock from the Python reference implementation. The 12 v0.1 conformance vectors at github.com/studio-11-co/falsify document the byte-exact expected output for canonical inputs. No data leaves your browser unless you click Anchor publicly. /check runs heuristic claim analysis · /integrity shows scored real-world claims · spec.falsify.dev/v0.1 is the canonical specification.