| · APPLIED COMPUTE · STATEMENT OF WORK ·
Statement of work
The contract terms the proposal depends on: what is in scope now, how the customer keeps control as the engagement grows, and when the deal is re-papered.
Intent
Commit only to a defined scope now, with objective acceptance and milestone invoices. As the work grows, explicit triggers make expansion a new order, not a silent change in scope.
Short term and long term
| Now (this order) | As the customer expands |
|---|---|
| Scope is one workflow and one model. | A new model, method, region or topology needs a new order. |
| The customer decides after each cycle whether to continue. | Production is a separate order with its own envelope. |
| Acceptance rests on objective evidence (run IDs, graded metrics, a signed handoff). | Scale reviews start at 80% of the envelope, before capacity runs out. |
| Invoices follow signed milestones; early exit pays approved work and committed third-party compute. | Any change of scope goes through the amendment triggers in section 5. |
Thought process
- Stop rules belong to the customer. A score can prompt a review, but it never stops contracted work on its own. This keeps the customer in control without giving them a free exit after the work is paid for.
- Pay for finished work. Milestones match the phases in the proposal, so the invoice and the deliverable line up one for one.
- Re-paper on named triggers. Section 5 of the SOW lists the triggers. Each one is a reason to re-scope and re-price the work.
The customer copy
Open the customer copy in its own tab · print from there for a clean copy.