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

# MRC 66: Zion As The Next Morpheus Era

Proposal to use "Zion" as the naming for the New Era that includes the MVM and the Reference Implementation.

This naming is consistant with the themes of Morpheus where Zion is the city of freedom those building freedom tech are working toward building together.

This era is focused on delivering the Morpheus Virtual Machine and the Reference Implementation Freedom Agent.

## MVM:

* Inference router & marketplace (already delivered in previous eras)
* Agentic Tools Marketplace as described in MRC 60. <https://github.com/MorpheusAIs/MRC/blob/main/MRC60.md>
* Data storage router and marketplace as described in MRC 62. <https://github.com/MorpheusAIs/MRC/blob/main/MRC62.md>

## Reference Implementation Agent:

A user facing Agent that offers an example to Agent developers of how to integrate the compenents of the MVM. Described in MRC 63. <https://github.com/MorpheusAIs/MRC/blob/main/MRC63.md>


---

# 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://gitbook.mor.org/mrc/drafts/mrc66.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.