> For the complete documentation index, see [llms.txt](https://docs.nerve-protocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nerve-protocol.com/overview/roadmap.md). # Roadmap This roadmap tracks Nerve Protocol's phased development from initial enclave infrastructure through a globally distributed, sovereign AI compute network. Phases are time-bounded and milestone-driven. Each phase's completion criteria are defined before work begins. *** ## Phase One — Q4 2024 to Q4 2025 **Status: Completed** Phase One established the foundational infrastructure: the enclave-first execution backend, the initial model stack, and the closed preview environment. All Phase One milestones were completed before the public beta launch. * Designed and deployed the enclave-first backend and secure API fabric * Provisioned TEE-backed infrastructure and core agent APIs across initial node clusters * Curated private training datasets and completed initial model training for Myelin and Soma * Established zero-leak telemetry and continuous feedback loops across enclave sessions * Completed a closed preview program with early enterprise partners * Launched the Nerve beta console with hardware-enforced enclave privacy * Optimized inference pipelines for low-latency enclave responses * Standardized remote attestation formats and compliance proof schemas across jurisdictions *** ## Phase Two — Q1 2026 to Q2 2026 **Status: In Progress** Phase Two delivers the public-facing product layer: the unified operator dashboard, production model releases, and the early access expansion. Zero-knowledge personalization and initial mobile infrastructure are active development priorities. * Launched Soma (32B) and Myelin (4B) into public beta inside sealed enclaves * Rolling out the unified Nerve dashboard and encrypted control interfaces * Expanding the early access pool and processing production operator feedback * Deploying zero-knowledge personalization that retains session context without data leakage * Developing secure mobile components with tunnel access to active enclave sessions * Establishing data provider partnerships under zero-knowledge query contracts * Releasing multi-agent orchestration for enterprise and sovereign operation use cases * Building secure voice-to-text pipelines processed entirely within the enclave boundary * Releasing core developer SDKs for custom enclave module construction *** ## Phase Three — Q3 2026 onwards **Status: Planned** Phase Three scales Nerve Protocol into a globally distributed, edge-native intelligence network. The Nerve Sovereign Cloud — a user-owned encrypted compute mesh — is the capstone milestone of this phase. * Deploying regionalized enclave hubs with latency-bounded execution guarantees * Launching federated model architectures for edge inference without data exfiltration * Integrating voice, persistent private memory, and local-first execution into a unified agent interface * Expanding developer ecosystem with certification programs and third-party tooling support * Bridging cross-chain networks for borderless, chain-agnostic agent workflows * Opening the Enclave App Marketplace for vetted third-party agents and private data services * Initiating v2 research on predictive intelligence models for finance, healthcare, and regulated sectors * Launching the Nerve Sovereign Cloud: an encrypted, distributed compute mesh for enterprise-grade private AI *** *Roadmap timelines reflect current planning and are subject to change based on production feedback, infrastructure findings, and protocol-level decisions. Material changes will be announced through official channels.* --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.nerve-protocol.com/overview/roadmap.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.