> 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/vvc-request-for-additional-information.md). # VVC Request for Additional Information If the VVC determines that additional information is need beyond what has been submitted in the project plan, monitoring report, and any submitted supplemental information that request must be done via email or via a shared document that will then be saved and added to the documents associated with the credit approval and linked to the Regen Ledger. Required documents for Validation and Verification must be submitted via the [Project Information Submission Form](/regen-validation-and-verification/regen-registry-verification-and-validation-manual.md). Regen Registry will as needed provide NDA's for parties to sign as well as label and classify documents as "Confidential", "Internal Use Only" to indicate level of sensitivity. These documents should be watermarked as such by those submitting the documents. --- # 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/vvc-request-for-additional-information.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.