Scope-creep clause for AI vendor contracts

You are drafting the scope-creep handling clause for an AI engagement contract. Most vendor contracts handle scope-creep adversarially or vaguely. Yours should be clear AND preserve the working relationship.

CONTEXT
- The engagement scope as agreed: {{agreed_scope}}
- Things explicitly out of scope: {{out_of_scope}}
- Project value: {{project_value}}
- Engagement length: {{engagement_length}}

OUTPUT (full clause, in this order)

**1. Definitions.**
- "Scope" - reference the SOW section that defines what was agreed.
- "Clarification" - a request that asks the vendor to elaborate, document, or explain something within the agreed scope. No charge.
- "Refinement" - a small adjustment that improves an in-scope deliverable. No charge if under [X hours].
- "Change order" - a request that adds, removes, or materially changes a deliverable. Priced before work begins.

**2. The free-vs-priced line.** A specific, defensible standard. Examples to consider:
- Up to {{free_threshold}} hours of refinement work per deliverable is included.
- Anything that changes acceptance criteria is a change order.
- Anything that adds a new integration, new data source, or new user role is a change order.

**3. Change-order process.**
- How a change is proposed (template, fields).
- Vendor response time committed (e.g., 3 business days).
- Pricing standard (hourly + materials, or fixed-fee scoping fee).
- Approval threshold (under $X auto-approved by named role; above $X requires steering committee).

**4. The clarification log.** A shared document that captures clarifications so the next disagreement has a record. Who maintains it, where it lives, how it's reviewed.

**5. Disagreement escalation path.** Three steps:
- Working leads discuss within 3 business days.
- If unresolved, sponsors meet within 7 business days.
- If still unresolved, the named third-party arbiter or mediator engages.

**6. The "good faith" clause.** One paragraph stating both sides commit to interpret ambiguity in favor of the spirit of the engagement, not the strictest reading of the SOW. This is the clause that preserves the relationship.

**7. Practical example.** A short worked example showing how a specific hypothetical scope-creep request would flow through this clause.

VOICE
- Contractual but human. Both parties should be able to read this and feel fairly treated.
- No em-dashes.
- No "leverage," "unlock," "navigate," "robust," "seamless," "cutting-edge."