HAPPIVERSE · node 001 · HAPPI/1.3

Don't trust it — witness it.

This page lets you, with no account and nothing of ours installed, re-check that node 001's AI-decision chain — a HAPPI/1.3 signed IDR artifact demonstrating cryptographic causation — was signed and has not been altered. Your own browser does the maths below — we cannot fake the result for you.

Checking the signature in your browser…

What just happened, in plain words:

Your browser loaded a small bundle, took node 001's public key, and used it to verify a digital signature over the summary of its IDR decision chain. A public key can only check a signature — it can never create one — so a green result means the chain was signed by the holder of the matching private key (which never leaves node 001) and not changed since.

The signed IDR decision chain

Each row is an Intent Decision Record (IDR) — metadata only: which public API route was called, which provider/model answered, the outcome, and when. No message content is ever published. The rows link by hash (each carries the previous row's hash), so removing or editing any one breaks the chain visibly.

#routeprovidermodelstatuswhen (UTC)entry hash

The tamper button edits a row in memory and re-runs the exact same check. It proves the verdict is real: change one byte and the signature no longer matches. (Nothing is sent anywhere; it only changes what your browser holds.)

What this proves — and what it does not (read this)

node 001 is movement-first, not a uniqueness claim.

This proves one node's own signed IDR chain — one leg of cryptographic causation.

This page verifies a HAPPI/1.3 signed IDR-chain bundle — the IDR leg of cryptographic causation (IDR = what the AI decided; memory-chain = what it believed; cite.verify = every claim provable against its source). The check uses your browser's built-in WebCrypto (crypto.subtle.verify, Ed25519) against the published public key. The signing key stays on node 001 and never appears here. The local tamper-evidence layer is HMAC; this public proof layer uses asymmetric Ed25519 — the only scheme a stranger can verify without a shared secret. Bundle: node-001-bundle.json.