Enter an attestation ID to verify the complete cryptographic chain — from AI decision to immutable Hedera record. Independently verifiable. No trust required.
All decisions in this batch are compressed into a single cryptographic commitment. Any modification produces a different root — making tampering detectable.
Signed with ML-DSA-65, NIST FIPS 204. Resistant to quantum computing attacks. The signature cryptographically binds the forest root to this oracle's identity.
Written to Hedera Consensus Service — a public, permissionless ledger governed by the Hedera Council. No single entity can alter or delete the record.
The page above traces one attestation to its ledger record. This is the product that puts your agent sessions in that position and keeps them there.
The property underneath all three, tamper-evident chronological ordering that any party can verify, is aligned with the electronic ledger trust service category the EU's revised eIDAS regulation (2024/1183) now formally recognises. Rubric does not claim qualified trust service status; the category simply gives regulators a legal vocabulary for what these records are.
One session, anchored on 2026-08-30. One escrow envelope. Then the machine was wiped and the evidence came back from a 201-byte key file. Both anchors below are real. Check them without us.
The consensus timestamp is assigned by the network. Rubric cannot backdate it.
Every tier: your key, our ciphertext. Rubric cannot read your evidence, and recovery never requires our cooperation. That is not a policy. It is the architecture.