> 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-development-support.md). # Protocol Development Support Support during the stages of Methodology Development Regen Registry supports protocol developers during the process of protocol development through internal support, facilitation of an Expert Review process and access to our broader community network. Throughout the process of protocol development, [Regen Registry’s Hylo](https://www.hylo.com/groups/regen-methodology-development) and [Twitter](https://mobile.twitter.com/regennetworkdev) spaces will serve as community conversation spaces. These spaces allows for sharing updates on the latest news in all things Regen Registry: cutting edge protocols, carbon accounting, nature-based solutions, biodviersity credits, crypto and more. The RND community of scientists, Earth stewards, technologists and more engage in these spaces. **Support:** Throughout the protocol development process, Regen Registry will provide email and call check-ins. These check-ins occur at the discretion of Regen Registry or as requested by the developer to address timeline, feedback and process questions. Regen Registry also works to connect protocol developers with targeted people and organizations in our network who can support the development of the protocol through active community networking and co-working spaces. --- # 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-development-support.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.