Statement of Work
Prepared for Example Enterprise · Take-home submission draft, not an official Applied Compute document.
1. Parties and scope
| Customer | Example Enterprise |
| Provider | Applied Compute |
| Workflow in scope | Internal workflow automation |
| Base model | Qwen3.6-35B-A3B (open-weight; access and licence per Section 6) |
| Method | GRPO reinforcement learning |
| Approved RL cycles | 3 (every 1 week); change orders required beyond 3 |
| Planned duration | 6 weeks |
| Hosting region | US region TBD |
2. Phases, responsibilities and acceptance evidence
| Phase | Applied Compute delivers | Customer owns / approves | Evidence to accept |
|---|---|---|---|
| 1 · Setup package Weeks 1–2 | Frozen evaluation set, grader, environment and baseline score; go/no-go gate. | Co-design and sign-off of evaluation and grader. | Versioned grader and harness, reproducible baseline run ID, signed go/no-go. |
| 2 · Managed RL cycles 3 cycle(s), one every 1 week(s) | Train, rollouts, held-out evaluation and the agent platform, with the included compute and usage allowances. | Explicitly chooses to stop or continue after each cycle. | Run ID, usage ledger against the allowances, graded metrics, failure samples, signed cycle decision. |
| 3 · Independent handoff Week 6 | Final evaluation on untouched data; checkpoint, configuration, traces and runbook. | Accepts delivery by checking the listed artifacts. | Reproducibility report, model version, delivered files and signed handoff. |
3. Stopping rules and decision authority
- Success target: held-out score of 80% on the frozen evaluation (Held-out pass rate). Reaching it triggers a review, not an automatic stop.
- Plateau: gains below 1.0 percentage points for 2 consecutive cycles trigger a review.
- Cycle cap: 3 cycles pre-authorised. No score threshold stops contracted work automatically.
- Only the customer decides whether to continue or stop after each cycle. Decision owner: customer product / SME lead.
4. Commercial schedule
Invoices follow the milestones below. Payment terms: [net terms: counsel review].
The maximum committed fee is $247,247. Usage above the allowances needs your written approval and is capped at $25,000 in total without a change order. This price is valid for 30 days from issue.
| Invoice | When | Amount | Running total |
|---|---|---|---|
| Setup gate | Week 2 | $49,449 | $49,449 |
| Cycle 1 of 3 Managed cycle, usage included | Week 3 | $57,691 | $107,140 |
| Cycle 2 of 3 Managed cycle, usage included | Week 4 | $57,691 | $164,831 |
| Cycle 3 of 3 Managed cycle, usage included | Week 5 | $57,691 | $222,522 |
| Handoff and verification | Week 6 | $24,725 | $247,247 |
| Total training fee | $247,247 | $247,247 |
What is included, and usage above it
Your total covers everything in the three phases. The included usage is:
| Managed compute | 3,870 GPU-hours across the engagement |
| Agent platform usage | 172.5 million tokens |
Usage above these allowances is billed only with your written approval, up to $25,000 in total, at:
| Managed compute above the allowance | $8 for each GPU-hour |
| Agent platform usage above the allowance | $14 for each million tokens |
Every cycle score report shows usage so far against the allowances, so there are no surprise charges. Rates are fixed for this statement of work; any later order is priced at the rates then current.
5. Amendment and re-papering triggers
The following require a written amendment before work proceeds:
| Trigger | What happens |
|---|---|
| New base model or method | Re-confirm model fit, memory, unit rates, training throughput and evaluator comparability; sign a revised order. |
| More cycles or higher token volume | Written change order before exceeding the approved cycle count or compute allowance. |
| New workflow, data regime or grader | Re-scope data rights, acceptance benchmarks, engineering and timeline. |
| Different region, isolation or GPU topology | Reassess availability, security posture and price. |
| Production launch or SLA upgrade | Separate serving order with latency targets, traffic envelope, availability and minimums. |
| Production demand above the contracted envelope | Review at 80% of capacity; amendment before adding replicas or exceeding contracted traffic. |
| Customer pause or termination | Customer covers approved work and any non-cancellable third-party compute commitments made for this engagement, net of reasonable redeployment. |
6. Customer responsibilities and assumptions
- Customer provides data and access by kickoff, and confirms the base-model licence and training access.
- Scope is limited to the one workflow above. Material changes follow Section 5.
- Results are reported as measured on the frozen held-out set. A quality uplift is not guaranteed.
[Data rights and confidentiality: counsel review] · [Liability and indemnity: counsel review] · [Termination payment: counsel review] · [Governing law: counsel review]
Signatures
| For Example Enterprise | For Applied Compute |
| Name / title / date: | Name / title / date: |