> 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/governance.md). # Governance As the governing body, the VVC ensures that projects adhere to Regen Registry Program and the applied protocol/methodology. Through careful evaluation and adherence to the guidelines set forth in the Validation & Verification Manual, the VVC upholds transparency, fairness, and maintains the highest standards in certifying credits to support environmental regeneration. VVC members must adhere to the requirements for timely response and communication as outlined in the contract they sign with the Project Proponent. The assigned consultant will be responsbile for reporting any failure to do so that may result in termination of contract. In this case, the VVC will need to pause progress until a new committee member is contracted. --- # 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/governance.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.