# Pilot commercial terms and scope — negotiation template

**Status:** non-binding discussion template. It is not legal advice, an offer,
an executed agreement, partner acceptance, or authorization to deploy or send
value. Counsel and authorized signatories for both parties must approve the
final agreement.

## Prepared scope

| Item | Prepared boundary | Must be completed in an executed agreement |
|---|---|---|
| Pilot | Base, chain ID 8453; one explicitly allowlisted design partner maximum | Partner legal name; candidate ID; start/end dates |
| Purpose | Limited technical evaluation against agreed success criteria | Use cases, acceptance tests, owners, decision date |
| Writes/value | Not authorized by this package; V2 remains default | Approved methods, caps, maximum loss, funding source, addresses |
| Exclusions | Production claim, Solana, cross-chain value flow, surveillance, freeform personal data | Any additional exclusion required by counsel or partner |
| Data | Minimum necessary; public-chain data is public and durable | Data map, roles, retention, deletion/return, subprocessors, transfer terms |
| Support | Tier must be selected in writing; no tier is active by default | Coverage, response targets, channels, contacts, fees |
| Exit | Bounded, documented wind-down; no silent rollover | Notice, maximum exit window, data handling, final reconciliation |

## Commercial schedule to complete

- Fees, currency, taxes, invoicing cadence, payment due date, expenses, and
  refund/credit terms: **TBD by authorized commercial owners**.
- Pilot term, renewal (if any), termination for convenience/cause, and maximum
  wind-down period: **TBD; no automatic production conversion**.
- Liability allocation, warranties/disclaimers, indemnities, confidentiality,
  IP/license terms, publicity, governing law, dispute process, and force
  majeure: **TBD by counsel**.
- Insurance types, limits, carriers, certificates, and notice duties:
  **external evidence required; no coverage is claimed**.
- Success criteria and acceptance procedure: **TBD and must be bilateral**.
  Silence and use are not acceptance.

## Scope-change rule

Every change requires a written request, impact assessment (security, privacy,
commercial, operational, V2, cap/maximum loss), named approvals, effective
date, rollback/exit effect, and a new candidate binding when code, deployment
manifest, or released scope changes. Email or meeting discussion alone does not
activate a change unless the executed agreement expressly defines it as a valid
approval mechanism.

