> For the complete documentation index, see [llms.txt](https://yvechat.gitbook.io/wp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://yvechat.gitbook.io/wp/roadmap.md).

# Roadmap

Progress is organized into named eras. Each one completes a layer of custody.

<figure><img src="/files/hnRVKpiAcBDLXjaz8v7Y" alt="Five eras"><figcaption><p>Each era hands another layer of control to the user</p></figcaption></figure>

***

```mermaid
graph LR
    A["Custody"] --> B["Engine"]
    B --> C["Gateway"]
    C --> D["Network"]
    D --> E["Sovereignty"]
```

***

### The Eras

| Era             | Focus               | Key deliverables                                                                                                                                                                                                                                        | Progress                                                                                                    |
| --------------- | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
| **Custody**     | The foundation      | <ul><li>Workspace with threads and model switching</li><li>Local accounts and optional wallet authentication</li><li>Local conversation storage</li><li>Tool credentials held in the Engine</li></ul>                                                   | Delivered                                                                                                   |
| **Engine**      | Local inference     | <ul><li>YveChat Engine with explicit six-digit pairing</li><li>Ollama discovery, model listing, validated pulls</li><li>Runtime status and capability filters</li><li>Local same-origin fallback interface</li><li>ComfyUI image generation</li></ul>   | Delivered, with signed public installers outstanding                                                        |
| **Gateway**     | Tools with consent  | <ul><li>Web search with clickable citations</li><li>Page and PDF reading</li><li>Sandboxed code execution</li><li>MCP connections with per-tool permissions</li><li>Sovereign Pass and gateway credits</li></ul>                                        | In progress. Search delivered, page and PDF tools implemented in the gateway, execution and MCP outstanding |
| **Network**     | Shared capacity     | <ul><li>Full vLLM discovery and capability mapping</li><li>Hosted-provider credential management</li><li>Agent and MCP marketplace</li><li>Opt-in compute network settled in <code>$YVE</code></li><li>Team workspaces over user-held storage</li></ul> | Planned. vLLM is reachable today as an experimental endpoint                                                |
| **Sovereignty** | Full self-direction | <ul><li>Governance over protocol parameters</li><li>Independent audits and bug bounty at scale</li><li>Encrypted multi-device sync</li><li>User-configurable external storage</li><li>Authenticated service connections</li></ul>                       | Planned                                                                                                     |

***

### Token Utility by Era

`$YVE` utility deepens as each era completes, described fully in [Utilities](/wp/yve/utilities.md).

| Era             | Utility introduced                                             |
| --------------- | -------------------------------------------------------------- |
| **Custody**     | Token generation                                               |
| **Engine**      | Sovereign Pass, unlocking the scaling tier                     |
| **Gateway**     | Gateway credits metering tool calls through operated providers |
| **Network**     | Marketplace settlement and compute network payment             |
| **Sovereignty** | Governance over parameters, emissions, and treasury            |

***

### How Progress Is Measured

Each era completes when its deliverables are usable by someone outside the team, on their own hardware, without assistance.

Adoption is measured by Engines paired and running, local models served, and threads persisted to user-held infrastructure. Those measure custody actually taken up, which is the only metric aligned with the position.

{% hint style="info" %}
Eras are sequenced by dependency. Timelines are indicative, reviewed quarterly, and adjusted as delivery and conditions require. Nothing here is a commitment to a date.
{% endhint %}

***

Five eras.

Each one moves another layer into the user's hands.


---

# 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://yvechat.gitbook.io/wp/roadmap.md?ask=<question>&goal=<endgoal>
```

`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.