What Evidentia makes verifiable
- Proof record integrity
- event_hash, signature, and timestamp consistency
- Merkle root consistency
- Chain-anchor consistency
- Evidentia’s own Platform Signing Key state
- Key usage history and Daily Platform Trust Roots
Trust infrastructure
Evidentia Trust Infrastructure
Evidentia records not only Proof records, but also its own platform signing key state, key usage history, daily trust roots, and external anchors.
What Evidentia does not prove
- That the AI decision itself was correct
- That submitted input was factually true
- Legal admissibility or regulatory compliance
- A mathematical guarantee that private keys were never exposed or misused
- That HSM/KMS is already active unless explicitly stated
Platform Trust Model
Evidentia records which Platform Signing Key was used to sign new Proofs and records key usage events. These records are summarized into a Daily Platform Trust Root and anchored externally, allowing others to verify that the published key state and usage history have not been altered after anchoring.
Platform Signing Key
Key Usage Ledger
Daily Platform Trust Root
External Anchor
Independent Verification
Current beta limitations
During Open Beta, Platform Trust Infrastructure is being introduced progressively. KMS/HSM-backed key protection, external attestation, and advanced key rotation audits are planned for future production hardening.
Daily Platform Trust Root
Evidentia records platform signing key state, key usage history, and key lifecycle events. After production release, Evidentia plans to anchor a Platform Trust Root externally once per day.
This allows independent verification that the published key state and usage history have not been altered after anchoring.
This mechanism does not mathematically prove that a private key was never exposed or misused. KMS/HSM-backed custody, key usage logs, and external audits are additional trust layers.