> 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/introduction.md).

# Introduction

Morpheus is being developed in an **open-source, community-driven way**, by contributors from all around the world.

These contributors are rewarded through the **Code Provider bucket**, which receives **24% of all protocol emissions**.\
Learn more about emissions distribution [here.](https://gitbook.mor.org/tokenomics/mor-emissions)

Open-source collaboration has fueled many of the greatest technological breakthroughs — from **Linux** and **Python** to **Ethereum** itself.

Morpheus follows this same philosophy, empowering anyone to contribute to the evolution of the protocol.

To make collaboration structured and transparent, the community uses the **MRC (Morpheus Request for Comments)** system — inspired by Ethereum’s **ERC (Ethereum Request for Comments)** standard.

MRCs allow anyone to **propose improvements, new features, or changes** to any part of the Morpheus ecosystem — from smart contracts and infrastructure to community tools and governance models.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://gitbook.mor.org/mrc/introduction.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
