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

# MRC 57: Best Practice For Stages Of Deployment Of A New Morpheus Reference Implementation Version

## Recommendation for Improved Flow / Moving Community Feedback / Testing To Earlier

Previously the flow of upgrades has been to design, code, test, audit and then enter community testing before deployment. However this has led to several examples of when a deployment is passed audits, however the community find issues after the fact right before deployment. To avoid this I'd propose the community feedback & community testing steps be moved up right after the design stage and and coding internal testing respectively.

## Stages of Development

* 1. Design a Version publish on Github.
* 2. Community feedback, final decision by maintainer.
* 3. Coding by selected Coder.
* 4. Internal Testing by Coder
* 5. Community Testing - final decision by maintainer
* 6. Final Audit.
* 7. Deployment of New Reference Implementation


---

# 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/closed/mrc57.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.
