SVSANNVIT
The proof asset

A sample chain of custody. Go ahead — tamper with it.

This is the record structure a regulator or opposing counsel would receive: the recommendation follows from the check, the check from the snapshot, the snapshot from the policy the AI actually read — each record sealed over the one before it. Every field below marked with a pencil is editable. Change anything. The chain re-verifies as you type, with real SHA-256, right here in your browser.

CHAIN VERIFIED. All four records match their seals. Edit any field below to see what tampering looks like.
record #0244 · 14:01:52 UTCSEALED

Source document — Investment Policy Statement, v3.2

dms://policies/IPS-v3.2.pdf
sealed sha256:…current sha256:…
record #0245 · 14:01:57 UTC · followed from #0244SEALED

Holdings snapshot — 41 positions

sealed sha256:…current sha256:…
record #0246 · 14:02:03 UTC · followed from #0245SEALED

Concentration check — §4.2 limit test

sealed sha256:…current sha256:…
record #0247 · 14:02:11 UTC · followed from #0246SEALED

Recommendation issued — human review sealed onto it

Approved — CCO, citing §4.2, §5.1
sealed sha256:…current sha256:…

What you just did is what an insider, an attacker — or an AI rewriting its own story — would try. In the product, the chain above is only the first plane: records are mirrored to an independent append-only store, cross-checked continuously, and anchored to external timestamp authorities (RFC 3161), so even the operator of the database cannot silently rewrite history. Your auditor verifies independently, without contacting us. In the live demonstration, we do this against the real product.

See it for yourself — thirty minutes, one sealed record altered live.

Book a demonstration →