Roadmap

What ships today.
What's next.
What needs specialists.

Most vendors hide their roadmaps. Verdifax publishes because every claim should be auditable , today by running the open verifier, and tomorrow by the same standard once specialists land.

▣ Shipped

Shipped today

Provable in production. Every item below is running on api.verdifax.com right now and independently verifiable.

SHIPPED

§0 Deterministic Attestation Contract

RFC 8785 canonical JSON + SHA-256. Same inputs always produce the same manifest hash, byte-for-byte. Cross-language test vectors verified by parallel Go and Python implementations.

RFC 8785Go + Python verified
SHIPPED

Core deterministic pipeline (DOG · DTL · DKEC · AER)

Stages 1-4: Deterministic Oracle Gateway, Transport Layer, Kernel Execution Controller, Attestation Execution Record. Every external input is canonically encoded, sequenced, dispatched, and aggregated into a tamper-evident record.

4 kernelsManifest sealing
SHIPPEDLIVE

AIVP, Live AI Verification Protocol

AI Verification Protocol governance running against the live Anthropic Claude API. Every governed run binds the AI output text into a sealed PIA hash. Adapter ID surfaced honestly in every audit PDF.

Live Claude APIPIA hashed
SHIPPED

PEPG + MCD, Pre-execution policy gating

Signed PSL policies evaluated before any kernel runs. Issues either a sealed AllowToken (admit) or a sealed DenyReceipt (reject). Threshold-signed policy support; malicious-content detector consulted on every evaluation.

PSLThreshold signing
SHIPPED

CCV + MACC, Runtime budget enforcement

Per-run + cumulative tenant budget monitoring. Halts mid-flight when token / cost / time limits breach. Sealed CCVHaltReceipt or MACCHaltReceipt preserves the original AllowToken hash + partial-execution hash.

Token budgetsSealed halt receipts
SHIPPED

NREP, Non-Repudiation Engine Protocol

Every execution is bound to a specific actor identity via Ed25519 signature over the AER. Public-key registered against the API key at first use; signatures verifiable offline.

Ed25519Non-repudiation
SHIPPED

CRES, Cryptographic Record Erasure

AES-256-GCM envelope encryption with per-record DEKs. Erasure destroys the DEK, plaintext mathematically unrecoverable, manifest seal preserved. 17 unit tests; designed for GDPR Art. 17 / HIPAA §164.530(j).

GDPR Art. 17HIPAA §164.530(j)
SHIPPED

CES + LTC, Compliance & legal evidence

Control & Enforcement System applies classification + retention to every run. Legal Translation Compiler maps manifest fields to a jurisdiction-correct LegalEvidenceArtifact with US (FRE 901, FRCP 26), EU (eIDAS, GDPR Art. 22), and UK (PACE 1984) claim sets.

FRE 901eIDASGDPR Art. 22
SHIPPEDNEW

Semantic Attestation Policy Profiles

Admission-time gap check: policies require specific AttestedContext fields before a run is admitted. Missing-field denials produce sealed AttestationGapReceipt artifacts. Four starter profiles ship today: healthcare, financial governance, internal audit, GDPR-aligned.

4 starter profilesAdmission-time gap check
SHIPPEDLIVE

Sigstore Rekor integration

Every successful run is committed as a hashedrekord entry on rekor.sigstore.dev, the same public transparency log used by the Linux kernel and major open-source releases. Production mode is live; the audit PDF discloses ledger mode honestly on every run, and the orchestrator halts hard on Rekor unreachability (no silent fallback to mock).

SigstoreProduction modeRFC 6962 Merkle
SHIPPED

Audit PDF + open-source verifier + SDKs

Receipt-style legal evidence document for every run. MIT-licensed verdifax-verify CLI recomputes every canonical hash offline. Four SDK clients (Python, Go, Node, R) with full parity, retry transports, and typed errors.

MIT verifierPython · Go · Node · R SDKs
SHIPPED

HSM-backed master key custody (AWS KMS)

The CRES master encryption key lives inside AWS KMS so the KEK is held in a FIPS 140-2 Level 2 HSM. Backs formal compliance claims under HIPAA §164.312(a)(2)(iv), PCI-DSS §3.5-3.6, FedRAMP, and NIST 800-53 SC-12/SC-13. Migration from Fly secret store completed.

FIPS 140-2 L2HIPAAFedRAMP
SHIPPED

Reproducible Docker TCU layer

Every base image SHA-pinned. Cargo with --locked, Go with -trimpath. SOURCE_DATE_EPOCH plumbed through Rust + Go stages. Standing CI 'double-build verification' gate. Customer-facing reproducer recipe published.

SHA pinningReproducible buildsCloses 80% of TCU
SHIPPEDLIVE

Trade reconciliation batch attestation

POST /execute/batch attests N rows in a single round-trip with per-row error handling. Single-transaction SQLite inserts (one fsync vs N) and aggregated per-tenant counter updates keep throughput high; PEPG, CCV, MACC, and AIVP halt receipts are preserved per-row. Demonstrated ~1,500 attestations/sec end-to-end against production. Real-time / microsecond HFT remains a specialist build, tracked on the specialist roadmap below.

POST /execute/batch~1,500/secHalt receipts
SHIPPEDLIVE

Reproducible-research toolkit

Category 6 ReproducibilityContext is bound into every audit bundle: runtime version, pinned dependencies, git SHA, declared random seeds, platform descriptor, optional container image hash. POST /execute/verify-determinism runs a payload twice and grounds the determinism flag on manifest-hash equality. Ships with Python (`pip install verdifax`) and R (`remotes::install_github("Verdifax/verdifax-sdk-r")`) wrapper SDKs, a Jupyter notebook, an R Markdown template, and the /research/ guide on docs.verdifax.com.

Python · R SDKsCat 6 audit bindingDeterminism check
SHIPPEDNEW

Formal verification, first milestone

11 machine-checked Lean 4 theorems on the canonical preimage encoder: determinism, byte-level spec conformance, order sensitivity, injectivity (no two distinct field lists share an encoding, under the null-free field discipline the runtime enforces), version binding, and the lifting of all guarantees to the hash layer under an explicit collision-freedom assumption. Kernel-verified on every commit by CI with a pinned toolchain. The full pipeline-determinism theorem, covering a model of all nine stages, remains on the specialist roadmap below.

Lean 411 theoremsCI kernel-checked
SHIPPEDNEW

Customer portal

Authenticated portal at verdifax.com/app: API-key login validated against the orchestrator, run history with search, full artifact viewer (every sealed hash, scaffold disclosures, Rekor anchor), audit-PDF download, browser-based sample attestation, and self-service key management (mint, scope, expiry, revoke). Admin surfaces carry an additional founder-only access gate. Access requests are approved by a human; approved requesters receive their key by email.

API-key authArtifact viewerKey management
SHIPPEDNEW

Hardware attestation, first platform (AMD SEV-SNP)

Runs sealed with the confidential-compute attestation service carry a real AMD SEV-SNP attestation report, bound to that specific run: the report's guest-controlled report_data field is derived from the run's envelope and AER hashes, so a quote can never be replayed against a different record. Before sealing, the orchestrator verifies the VLEK endorsement chain against AMD's Milan root of trust (pinned by fingerprint in the binary) and the report's ECDSA P-384 signature over its full body. The report, endorsement certificate, and AMD chain are embedded in the audit bundle so any third party can re-run all checks offline. Honest scope, stated in the artifact and every PDF: this is an attestation-service pattern. It proves genuine AMD hardware signed this run's identity, not that the orchestrator executed inside the enclave. Additional platforms (TPM 2.0, Nitro Enclaves) are on the specialist roadmap.

AMD SEV-SNPRun-bound quotePinned AMD root

◇ Deferred

Deferred

Scoped, not started. Each item is designed and ready to build but paused pending acquirer resourcing or first-pilot commitment. Listed publicly so buyers can see the next layer of scope they would inherit.

DEFERRED

Stripe webhook payment-state gating

API keys would provision in trial mode on first issue and promote to production on first paid invoice via Stripe webhook. Trial keys would carry lower per-run quotas so customers can validate integration before commercial commitment. Build paused; commercial gating shape will be set by the acquirer's billing posture.

Scoped, not startedAwaits acquirer / pilot

◌ Specialist track

Specialist roadmap

Real engineering, not marketing. Each item requires a specific specialist Verdifax doesn't yet have on the team. Listed publicly because honest sequencing matters.

Cryptography

SPECIALIST REQUIRED

Real ZK prover (winterfell STARK/FRI)

Replaces the deterministic R1CS hash facade with a real winterfell STARK/FRI prover. R1CS → AIR adapter, multi-prover equivalence, cross-toolchain reproducibility CI.

Specialist
ZK cryptographer
Timeline
3-6 months
SPECIALIST REQUIRED

Missing ZKSP proof steps

Transcript proof, hardware attestation proof, leakage upper bound. Each step requires defining a proof property mathematically and proving it preserves chain security.

Specialist
ZK cryptographer (plus hardware crypto for the attestation step)
Timeline
6-12 months
SPECIALIST REQUIRED

Formal verification: model-to-implementation fidelity

The Lean 4 development is shipped and public (github.com/Verdifax/lean-verdifax): the full tree, the pipeline_determinism and manifest_binding theorems over a model of all nine stages, and axiom-audit CI that rejects sorry and non-constructive axioms on every commit. What remains is the deepest step: machine-checked proof that the Lean model faithfully corresponds to the production Go and Rust implementations at the byte level (verified extraction or refinement proofs), so the theorems transfer from the model to the running code itself.

Specialist
Formal methods engineer (Lean 4, verified extraction)
Timeline
6-12 months
SPECIALIST REQUIRED

DEROT, Decentralized Root of Trust

3-of-5 threshold MPC quorum producing quorum-attested authorization. Threshold cryptography (BLS or Schnorr-based) and TEE-attested coordinator nodes.

Specialist
Threshold cryptographer
Timeline
3-6 months

Hardware

SPECIALIST REQUIRED

HRE, Hardware Root Engine multi-platform

Extends the shipped AMD SEV-SNP platform (see Shipped above) to TPM 2.0 and Intel TDX / Nitro Enclaves, plus migrating the orchestrator workload itself onto confidential-compute infrastructure (upgrading the shipped attestation-service pattern to in-enclave execution). Each platform has its own attestation primitives, certificate chains, and register semantics.

Specialist
Hardware engineer (secure-enclave)
Timeline
2-3 months

Distributed Systems

SPECIALIST REQUIRED

Spine, Network Determinism

Deterministic networking layer with zoned routing and Byzantine Fault Containment. Network-level determinism (no retries, no reordering across nodes) is research-grade work.

Specialist
Distributed systems engineer (networking + BFT)
Timeline
6+ months
SPECIALIST REQUIRED

Native Verdifax BFT Ledger

Bespoke 21-node Byzantine consensus implementing native Proof of Temporal Execution. Long-term replacement for the Sigstore dependency. Until it ships, runs anchor on Sigstore Rekor.

Specialist
Distributed systems engineer (BFT consensus)
Timeline
12+ months

Capital Markets

SPECIALIST REQUIRED

HFT-grade in-process attestation

Real-time / microsecond trading attestation. Replaces the per-decision REST round-trip with an in-process attestation library (Go / Rust / C bindings) that seals each decision locally, batches sealed records into a periodic uplink to the Verdifax orchestrator, and produces the same audit bundle shape as the live REST path. Unblocks the high-frequency trading TAM where current REST throughput (~thousands/sec) is insufficient.

Specialist
Performance / systems engineer (low-latency cryptography)
Timeline
3-6 months

Sustainability

SPECIALIST REQUIRED

Full CSRD / SEC Climate enterprise reporting

Multi-tier supply-chain carbon attestation across Scope 1, 2, and 3.1-3.15 with LCA database integrations (ecoinvent, GaBi, GHG Protocol product factor sets). TCFD and SEC Climate Rule reporting templates, supplier attribution graphs, automated emission-factor version pinning. Promotes ESG carbon attestation from POC scope to enterprise-deployable.

Specialist
Sustainability data engineer + LCA partnership
Timeline
6-12 months

Industrial Provenance

SPECIALIST REQUIRED

Vehicle lifecycle + EU Battery Passport attestation

VIN-anchored or battery-anchored event chains: manufacturing genesis, ownership transfer, recall remediation, repair lineage, odometer attestations, and EV battery health under EU Battery Regulation 2023/1542 (digital passport mandate, Feb 2027 deadline for ≥2 kWh industrial / EV batteries). Verdifax's existing DOG truth admission, PEPG policy gates, NREP actor signing, and AER lineage primitives apply directly. What requires specialist work: OEM / insurer / DMV ecosystem integration, real-time telemetry ingestion at vehicle-fleet scale, and production-grade hardware attestation that an ECU actually emitted the signed telemetry.

Specialist
Automotive industry partnership + production-grade hardware attestation
Timeline
12+ months (paced to EU 2027 deadline)

System Maturity Disclosure

Two open scaffold categories, named explicitly in every audit bundle.

Every Verdifax audit bundle names its open scaffold categories in the orchestrator code, surfaces them in every audit PDF, and prints them via the independent verifier under verdifax-verify --show-evidence-summary. Two remain open today:

  • ZK transcript (transcript.scaffold), activates when the winterfell AIR adapter ships and validates determinism across three Rust toolchains.
  • ZK proof binding (zksp_binding.scaffold), activates when the winterfell prover replaces the transitional R1CS hash facade with real STARK proof bytes.

Hardware attestation graduated from scaffold to real on its first platform. Runs sealed with the AMD SEV-SNP attestation service carry a verified, run-bound hardware quote (hardware_attestation.attestation_mode = "sev_snp") with the scaffold flag cleared; the quote, endorsement certificate, and AMD chain are embedded for offline re-verification. Runs sealed without the attestation service still disclose the scaffold honestly: the flag reports what each individual run actually carried.

Formal verification is no longer a scaffold category. Every new audit bundle carries a formal_verification record binding the run to the pinned Lean 4 proof development: repository, commit, toolchain, the kernel-checked theorem list (including manifest binding and pipeline determinism over the model), and the audited axiom footprint. The record is tamper-evident and run-bound, the independent verifier recomputes and checks it, and its scope statement says plainly that the theorems are about a model of the pipeline, with byte-format fidelity tracked on the specialist roadmap.

Full per-declaration detail, with the precise activation condition for each, is published at docs.verdifax.com/concepts/scaffold-gaps.

There is no silent fallback anywhere in the stack. The verifier's --strict mode exits non-zero whenever any scaffold flag is set, so a strict pass means every value in the bundle is rooted in real cryptography.

Want to discuss a roadmap item?

If a specific item is what your organization needs, whether it's shipping today or scheduled for the specialist roadmap, reach out. Pilot deployments help us prioritize what ships next.

Last updated: