Skip to content
MirrorFirm

What should a reseller ask for in a pilot of this workflow?

A checklist of what to request in a pilot sample: scope, layers, schema, labelled exceptions, held-out tasks, written licence terms, versioning and acceptance checks.

Use this list when you ask for a pilot, so the sample can be tested and the licence questions are raised early.

- **One domain and variant:** name a single setting, such as claim settlement or purchase approval, so the sample is coherent. - **Layers chosen:** decide between tables only, tasks with expected outcomes, or an environment with tool actions and reset. - **Schema and dictionary:** request the schema file, a key-integrity report and a short data dictionary with the sample. - **Labelled edge cases:** ask for boundary and exception cases to be included and labelled, so you can tell defects from intended behaviour. - **Held-out tasks:** if you plan to offer evaluation use, ask for held-out tasks to be kept separate from training material. - **Written licence terms:** put onward licensing, permitted customer use and withdrawal handling in writing before listing. - **Versioning:** agree how versions are numbered and how corrections are delivered. - **Acceptance checks:** decide your checks in advance, including a review for grounding and disclosure risk, since the output is generated.

A precise pilot request produces a sample you can test in your own pipeline and a clear decision on whether to widen the scope.

Audience:
Licensed resellers
Content type:
Checklist
Buyer question:
Scope and getting started

Content release: r-a220eb6e099b243b

More on Delegated approval