> 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/regen-validation-and-verification/regen-registry-verification-and-validation-manual/overview.md). # Overview For each validation and verification Regen Registry assembles an Validation & Verification Committee (VVC) of 3-4 members not associated with the project and that includes a local person that can do on the ground confirmation of adherence to the project plan, verification of monitoring procedures, and validation that local stakeholders were aware of and agreed to the project processes and procedures and have been informed of any financial benefits that the project may render and were informed on fund dispersement procedures. The VVC will work with the project proponents to answer a set of questions that will be used to validate and verify the project plan and data collected through the monitoring report. The VVC checks for adherence to the procedures outline in the protocol, the project plan, and required elements as outlined in the [Regen Registry Program Guide](https://regen-registry.gitbook.io/regen-registry-program-guide/). All requests for clarification from the EC to the project proponents must be documented as detailed as described in VVC[ Requests for Additional Information](/regen-validation-and-verification/regen-registry-verification-and-validation-manual/vvc-request-for-additional-information.md) chapter. --- # 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/regen-validation-and-verification/regen-registry-verification-and-validation-manual/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.