> For the complete documentation index, see [llms.txt](https://docs.coveragelabs.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coveragelabs.io/methodology.md). # Methodology - [Request Form](https://docs.coveragelabs.io/methodology/request-form.md): This is the starting point through which all engagements begin when a client submits a request for a quote. - [Scope of Work](https://docs.coveragelabs.io/methodology/scope-of-work.md): The scoping process is essential for accurately allocating resources, setting realistic timelines, and defining clear deliverables for the engagement. - [Rates](https://docs.coveragelabs.io/methodology/rates.md): This section details the base weekly rates for security reviews and fuzzing campaigns, determined by the agreed-upon number of engineers and the duration of the engagement. - [Statement of Work](https://docs.coveragelabs.io/methodology/statement-of-work.md): The Statement of Work outlines the key terms of the agreement between the client and Coverage, ensuring both parties are aligned. - [Communication](https://docs.coveragelabs.io/methodology/communication.md): This section outlines how communication is handled during our engagements, including the frequency and channels we'll use to ensure smooth and effective collaboration. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.coveragelabs.io/methodology.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.