> For the complete documentation index, see [llms.txt](https://handbook.regen.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.regen.network/protocol-development/protocol-methodology-development-overview.md).
# Protocol (Methodology) Development Overview
How to develop a protocol (also known as a methodology) with Regen Registry
The protocol details the credit type, credit unit, project activities, ecosystem type, monitoring, reporting and verification (MRV) process that is specific to a project.
As a methodology is being developed, the Regen Registry and Science Teams are available for limited internal feedback as part of teh Protocol Review process that as outlined below.
Please also join our [Hylo space](https://www.hylo.com/groups/regen-methodology-development) to engage in community support. See the [Methodology Development Support](/protocol-development/protocol-development-support.md) chapter for more details.
**Protocol Development Process:**
The development of a protocol includes:
* Research into existing approved methodologies in the [Regen Registry Methodology Library](https://handbook.regen.network/public-comment-upcoming-methods/) and those listed on other registries that may be similar, are tested and can be used as models for your methodology.
If using a methodology from an outside registry, it is the methodology developers responsibility to contact the author of the methodology to ask for permission to use that methodology. Cited resources and/or first hand interviews and accounts of regenerative work and observed successes from knowledgeable and experienced earth stewards in the projects specified ecosystem outline of researched monitoring approach including monitoring protocols and frequency description of verification process.
---
# 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://handbook.regen.network/protocol-development/protocol-methodology-development-overview.md?ask=&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.
