# Statement of Work

## Overview

Each Statement of Work includes, but is not limited to, the following components:

1. **Scope of Work**
   * For our engagements, we will reference a selected commit hash of the codebase and the files within scope for review.
2. **Deliverables**
   * For security-focused engagements, we will provide a report outlining key findings and insights. These may include technical assessments and supporting materials.
3. **Timelines**
   * Each engagement will have a defined start date and end date, followed by a two-week fix review period. During this period, the client can address identified issues, with our support for validation and assistance as needed.
4. **Engineering Team Breakdown**
   * Each engineer assigned to the engagement will be listed in the Statement of Work, along with their respective roles.
5. **Client Responsibilities**
   * Access and Resources: Ensure we have access to relevant repositories, documentation, and all necessary technical details that are essential for the engagement.
   * Timely Feedback and Communication: Provide prompt reviews and feedback on deliverables and maintain open communication throughout the engagement to address any questions or concerns.
   * Vulnerability Remediation: The client is responsible for deciding whether to fix or acknowledge identified vulnerabilities during the two-week fix review period, which begins after the preliminary report is sent.
6. **Price, Payment Schedule and Method**
   * Price: The total cost for the engagement is based on the number and level of engineers assigned, as well as the estimated duration of the engagement.
   * Payment Schedule: Payment is required in full upfront before the engagement starts.
   * Payment Method: We accept payments in USDT or USDC via selected networks.

Once both parties have signed the Statement of Work, a dedicated private communication channel will be established between our engineering team and the client's team.


---

# Agent Instructions: 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:

```
GET https://docs.coveragelabs.io/methodology/statement-of-work.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.