verify it yourself loading…

This page checks a nucleus agent's execution lineage — a hash-chained, Ed25519-signed edge log with a witness-cosigned Merkle anchor — entirely in your browser, against a trust anchor you pin. The verifier is the project's Rust code compiled to WebAssembly. Nothing is trusted but the hash function and the keys in your anchor; everything else is recomputed here, not believed.

Don't trust this page — prove it. Open DevTools → Network, toggle Offline, then click Verify. It still works: there is no server round-trip. The bundle below is real (generated and self-verified by examples/emit_demo_bundle.rs), not a screenshot.

fixture bundle.json (the agent's signed execution lineage) trust-anchor.json (the keys you pin — obtained out of band, not from the bundle)

loading verifier…

What this proves — and what it doesn't

✓ Proves: the lineage is internally consistent and tamper-evident (hash chain + Merkle inclusion), and was signed by the keys + cosigned by the witness in your trust anchor — i.e. integrity and authenticity of the record.

✗ Does NOT prove: that the agent behaved well, that information-flow policy held, or that any computation was correct. Tamper-evidence is not good behavior. The IFC enforcement and its machine-checked noninterference theorem are separate guarantees; this verifier does not evaluate them.

Source & reproducible build: sdks/verifier-js — rebuild the WASM with wasm-pack build --target web --release and diff it. The fixtures are emitted by cargo run -p nucleus-envelope --example emit_demo_bundle. No analytics, no third-party requests.