> 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/submitting-documents-for-review.md). # Submitting Documents for Review 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). This includes the Project Plan or Project Design document and Monitoring Report. All submitted documents will be recorded on Regen Ledger to transparently show the Validation & Verification process. 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. Regen Registry may offer services for encypted documentation as needed for data privacy and security. Contracts between the VVC, Regen Registry and Project Proponent members should establish a clear time frame for retaining sensitive data and outline protocols for securely disposing of information when no longer needed. A well-defined data retention policy ensures that sensitive information is retained only for necessary periods and is then securely destroyed. Regen Registry will regularly review and update document management policies to adapt to new technologies or legal changes is imperative. Keeping policies current ensures that sensitive information is consistently protected and managed in line with the latest standards and requirements. --- # 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/submitting-documents-for-review.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.