Development Roadmap

FPGA/TPM proof-of-concept. The Hardware Veto Core running on programmable logic — sub-microsecond deterministic veto with tamper-evident attestation. The software side is done and is the actual prerequisite: the veto logic is already a pure, side-effect-free module with zero I/O and zero global state, and its firmware API contract is published as a C header. What exists today is the engagement scaffolding — a statement of work for the deterministic-veto bitstream, a contractor shortlist, and a published silicon-partner kit. No bitstream has been built yet; this is a funded-partner milestone, not shipped hardware.

Attestation Marketplace launch. Multi-agent governance verification with Resilience Signatures, and the federated trust-exchange protocol live. The engine is implemented — roughly 2,500 lines across the governance and SDK layers, exposed through the trust-fabric API, with signed attestations, a revocation registry, and peer trust exchange behind a circuit breaker. Launch is gated on onboarding external attesters, not on writing the code: an attestation market with one participant is a log file.

Independent penetration test — contracted; scheduled 20 November 2026. Third-party black-box penetration test (OSSTMM methodology) against the public application surface, with risk-ranked findings and remediation tracking — scoped as part of the SOC 2 program and scheduled to run before the report is issued.

EU market readiness. The substrate already matches the shape EU AI Act compliance work needs — deterministic risk tiering, a declared AI system inventory, a vendor risk register, and per-decision evidence, surfaced publicly on the AI System Inventory. Which specific AI Act duties attach to EVE, and to a customer deploying it, depends on the role each party occupies and on how the system in question is classified; the platform is built to produce the evidence either way rather than to presume a classification. The data-protection paperwork is already substantive: a DPA with Article 28 processor clauses, Standard Contractual Clauses with the UK Addendum, a published subprocessor list with advance-notice and objection rights, and cryptographic deletion receipts. Three market-readiness items remain — the first two legal and contractual, the third genuine infrastructure work: appointing representatives under EU GDPR Article 27 and, separately, UK GDPR Article 27 — two distinct duties, each turning on where we offer services or monitor behaviour and on whether that Article’s own exception applies; on our present assessment neither exception covers us, and our privacy notice states plainly that no representative is yet appointed, adding DORA Article 30 contractual terms for EU financial-services customers, and standing up an EU data-residency deployment option — hosted production runs in a single region (us-east-1) today, with self-hosted and customer-VPC deployment as the current escape hatch.

Why it matters.

• Reduced enterprise procurement friction.
• Access to committed cloud-spend budgets.
• Faster security and vendor-review processes.
• Greater credibility with regulated enterprise buyers.
• Improved access to AWS and Microsoft partner ecosystems.

Continuing alongside — the listings are live without waiting on these.

• SOC 2 Type II attestation — audit in progress — and supporting trust documentation.
• Production-grade tenant provisioning and billing controls.
• Enterprise support and incident-response processes.
• Finalized commercial terms, SLAs, and marketplace pricing.

Where it stands.

• Marketplace seller accounts approved — AWS, Azure, and Google partner verification complete.
• Public listings live and transactable on AWS and Azure; Google Cloud available on contract.
• End-to-end subscription and provisioning flows in place.
• Public documentation reflects verified marketplace availability.
• Remaining commercial milestone: first marketplace private-offer or design-partner transaction.

Non-Provisional Utility Filing. Full patent prosecution of the filed provisional applications and pending invention disclosures in omnibus conversion bundles. Conversion window: Feb 22 – July 2027. Micro Entity status throughout.

Open verification standard. The evidence vocabulary is already versioned and stable: 149 eve.* schema versions spanning decisions, delegation, authority reports, assurance, lineage, AI-BOM, workload identity, and compliance packages — with independent verifiers in Python, TypeScript, and Go that check a record against a published public key and nothing else. The next step is publishing the schema set and a conformance suite, so a third party can verify EVE-issued evidence and issue EVE-compatible evidence of their own with EVE nowhere in the loop. A governance standard that requires trusting its vendor is not a standard — the proof has to outlive the relationship, and the format has to be checkable by someone who has never spoken to us.

Hardware enforcement research. Long-term research direction: compiling the deterministic veto core toward programmable logic and, potentially, purpose-built silicon. Exploratory — not on the near-term product roadmap.