This list belongs to starting-state fidelity, which uses an order partly shipped before a change request arrived. The introducer's part comes earlier: the starting-state fidelity scorecard decides whether to introduce, and the starting-state fidelity evidence gaps analysis explains what the packet should admit openly.
Packet order and owners
The order follows the logic of a simulation. AI developers begin each episode from a defined state, as Gymnasium's reset() does, and grade the end against a goal, as τ-bench does. The packet describes the same two ends using the company's records.
| Order | Document | What it shows | Prepared by |
|---|---|---|---|
| 1 | Task specification | The job each case represents | COO or VP operations |
| 2 | Event reconstruction note | Which events rebuild the order at any moment | ERP administrator with warehouse manager |
| 3 | Request record description | Where change requests arrive and whether their time is kept | Customer service lead |
| 4 | Allowed actions | What a responder may do, and who may approve what | COO with sales operations |
| 5 | Acceptance check | The test a correct response passes, fixed in advance | COO |
| 6 | Volume and span | Counts, years and migration dates | Operations analyst |
| 7 | Rights and sensitivity note | Identifiers present, contract limits, the authorizer | CFO or counsel |
Documents 1 to 3: defining the starting point
1. Task specification. "Respond to a customer change request on an open order, applying only the changes the order's state allows, and tell the customer what cannot be changed." One sentence is enough; it sets what every case will be graded on.
2. Event reconstruction note. The event types needed to rebuild an order at the request's received time: order creation, line edits, picks, shipments, address changes and invoice issue. For each, state whether it carries a timestamp, a user and an order line reference, and which system holds it. Warehouse and carrier systems often keep better times than the order desk, so name all of them. Toloka's description (checked 2026-10-18) of versioned environments and audit logs for exact reproduction is a fair benchmark for the detail a buyer will look for.
3. Request record description. Where change requests arrive (email, portal, phone notes, EDI) and whether the received time is stored on the order or only in an inbox. Give rough shares by channel if known.
Documents 4 and 5: what was allowed, and what counts as correct
4. Allowed actions. The moves available to a responder: cancel open quantity, add lines, change the address for unshipped lines, offer a return authorization for shipped goods, escalate pricing changes to a named role. Order systems usually enforce part of this; Shopify, for instance, lets merchants edit unfulfilled items but not remove fulfilled items or change their quantity. Record who may approve returns and credits, and up to what amount.
5. Acceptance check. Written before any outcome is examined, so nobody fits the rule to the result. Illustrative, using the main guide's 10:42 order:
- ☐No change is applied to quantity already shipped at the received time (the 150 glove cartons stay shipped).
- ☐Open quantity is adjusted as requested (the 50 open cartons are cancelled).
- ☐The address change applies only to unshipped lines (the first-aid kits).
- ☐The customer is told in writing which parts could not change.
- ☐Any return offer, such as for 30 cartons, is approved by a permitted role.
A response that edits the shipped line to 120 fails the first condition whatever the customer later accepted.
Documents 6 and 7: scale, span and rights
6. Volume and span. Change requests per year; the share arriving after partial shipment, if known; years of timed event history; and the date of any ERP or warehouse system migration, with a note on whether timestamps and edit history survived it.
7. Rights and sensitivity note. Customer names, site addresses, pricing and contact details appear throughout. List customer contracts that limit reuse, any third-party logistics provider that holds shipment logs, and the executive who can authorize a licensing discussion. Owners sometimes ask whether licensing such records makes them a data broker; the explainer on what a data broker is under state law answers that, and data licensing and cyber insurance coverage covers a question CFOs raise next.
Illustrative cover sheet
Fictional, for a 460-person foodservice equipment distributor.
| Field | Entry |
|---|---|
| Task | Respond to change requests on open orders within what the order state allows |
| Timed events | Picks and shipments timed in the warehouse system for five years |
| Edit history | Order-line change log active for three years, with old values |
| Requests | About half via portal with received time; the rest by email |
| Allowed actions | Returns approved by branch managers up to a set limit; pricing to sales operations |
| Migration | Warehouse system replaced four years ago; earlier history dated only |
| Authorizer | CEO, with the COO preparing the case |
Browser-based order portals produce a related kind of record, described in browser agent training data. Eligibility still applies: 50 or more full-time employees at peak, documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. Other record families are under data types.
Next step
Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If the operations lead could fill the event reconstruction note and acceptance check from systems already in place, register as a partner, confirm the company against who qualifies and read the terms, then introduce the COO and let the company prepare the packet with SourceX.