# Statements of Work

### Purpose

The Statement of Work is the execution unit of delivery.

It defines exactly what we are delivering, how delivery will be governed, and how acceptance and payment will work.

### Required Sections

Every Statement of Work should include:

* title
* parties
* background
* objectives
* scope
* out of scope
* deliverables
* milestones
* timeline
* roles and responsibilities
* assumptions
* dependencies
* customer responsibilities
* acceptance criteria
* payment schedule
* change control process
* IP treatment
* security requirements
* data handling requirements
* governance model
* reporting cadence
* termination consequences
* order of precedence

### Scope Standard

Scope must be written clearly enough that both parties understand:

* what will be delivered
* what will not be delivered
* what inputs are needed
* what assumptions apply
* what acceptance means
* what happens if requirements change

### Acceptance Standard

Each deliverable must have acceptance criteria.

Acceptance criteria should be:

* objective
* testable
* linked to the deliverable
* time-bound
* capable of evidence
* agreed before work starts

### Payment Standard

Payment triggers should align to clear milestones or deliverables.

Payment should not depend on vague or uncontrolled events.


---

# 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://framework.aic.io/company-operating-manual/commercial-and-contracting-model/statements-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.
