The proof layer for AI
AI decisions you can prove.
Verdifax converts AI execution into independently verifiable proof, auditable by regulators, courts, and counterparties.
The problem
AI systems make decisions that affect money, health, and national security.
When those decisions are questioned, there is no reliable way to prove what happened. Logs can be altered. Models can’t explain themselves. Evidence breaks the moment it’s needed most.
The proof
Every decision, sealed into something an outsider can verify.
Verdifax records every step of an AI decision, seals it into a cryptographic artifact, and produces a hash anyone can independently verify, without trusting us, the model, or the operator.
- Stage 1Input
- Stage 2Decision
- Stage 3Execution
- Stage 4Evidence
- Stage 5Seal
- Stage 6Verifiable Hash
The hash is the seal. Re-running the same inputs reproduces it byte-for-byte.
Who it’s for
Built for institutions that cannot afford to be wrong.
01
Defense & Intelligence
Targeting decisions, sensor fusion, and intelligence summarization with sovereign-grade evidence chains.
02
Healthcare
Clinical AI decisions backed by tamper-evident records that satisfy 45 CFR § 164.312(b).
03
Financial Services
Credit, AML, and trading models with cryptographic change-evidence aligned to SOX § 404 IT controls, SR 11-7 model risk, and ISO/IEC 42001 AI management.
04
Federal Civilian
EU AI Act Article 12 logging and Article 13 traceability, NIST AI RMF Govern + Measure evidence, and FedRAMP attestation for high-risk AI systems.
The difference
Logs ask you to trust. Verdifax lets you verify.
Others
Verdifax
Logs
Cryptographic proof
Trust the vendor
Verify independently
Explanations
Evidence
Best-effort audit trail
Sealed manifest hash
Technical foundations
Four properties that turn AI output into evidence.
Deterministic Execution
The same inputs always produce the same hash. Reproducibility is a primitive, not a goal.
Independent Verification
Any third party can recompute the manifest hash offline using the open-source verifier, no Verdifax credentials, no server trust required.
Cryptographic Sealing
Every input, every step, and every final artifact is collapsed into a single tamper-evident manifest hash.
Public-Log Anchoring
Each run is publishable as an immutable entry on Sigstore Rekor, the same public transparency log used by the Linux kernel and major open-source releases.
Outcome matrix
Five sealed outcomes. One verifier.
Every Verdifax run resolves to exactly one of five outcome states. Each state is backed by its own cryptographically sealed artifact recording the rule, the data, and the cost. The same verdifax-pepg-verify command verifies all five, independently of the orchestrator that produced them.
Allow
Pre-execution policy passed. The run proceeds and produces a sealed AllowToken bound to the policy hash and the rule that admitted it.
Sealed artifact
AllowToken
Deny
Pre-execution policy rejected the request. A sealed DenyReceipt records the fired rule, decision reason, and policy hash, replayable by anyone holding the policy file.
Sealed artifact
DenyReceipt
MCD-Fail
The prompt matched a curated threat signature in the Malicious-Content Detector library. The DenyReceipt carries the signature finding hash so the match is independently auditable.
Sealed artifact
DenyReceipt + MCDFinding
CCV-Halt
Continuous Constraint Verification halted the run mid-flight when a per-run budget, tokens, latency, cost, was breached. The CCVHaltReceipt seals the partial execution at the halt point.
Sealed artifact
CCVHaltReceipt
MACC-Halt
Multi-Agent Coordination Constraint halted a run that would have taken a tenant past its cumulative cross-run budget. The MACCHaltReceipt records the cumulative consumption and the contributing run.
Sealed artifact
MACCHaltReceipt
Specifications: PEPG_PSL_SPEC v0.2 (allow / deny / MCD-fail) · CCV_SPEC v0 (per-run budget halt) · MACC_SPEC v0 (cumulative tenant halt). Every outcome carries a self-attested build provenance block , orchestrator version, git SHA, SLSA level, builder identity, so the artifact tells you which binary produced it.
Three lines, then you have proof
Real product. Today.
The Verdifax SDK ships in Python today, with native bindings for Go and Rust. Three lines of code turn any AI inference into a sealed, independently verifiable run.
import verdifax
receipt = verdifax.attest(
payload="hello verdifax",
program_id="...",
route_id="...",
registry_record_hash="...",
)
print(receipt.manifest_hash)Engage
Build AI you can defend.
Verdifax is currently engaged with select institutions in defense, healthcare, and financial services. Access is granted on a case-by-case basis.
access@verdifax.com