What does a bounded reseller pilot look like?

A marketplace curator scopes a pilot around a retail returns rule. POL-091 permits a particular return route; POL-092 removes that route for requests lodged after its effective date while preserving requests already accepted. Return RET-0412 was accepted earlier, while RET-0413 remains an unsubmitted draft.

The reseller asks for generated policy text, return records and an agent task that selects the permitted route for each case. The pilot uses a downloadable task pack because that is the intended customer delivery path. Warehouse execution, refund settlement and broader consumer law interpretation sit outside the agreed task boundary.

The state change is narrow: the governing return route changes for newly lodged requests. The consequence is equally concrete: the agent must preserve the accepted route for RET-0412 and select an allowed route before lodging RET-0413.

Pilot review can examine whether customers understand the task, can load the package and can distinguish the two outcomes from supplied evidence. Expansion would then follow an identified need, such as adding an approval exception. The pilot teaches whether the reseller's proposed product has a useful operational unit before adding more policy families or domains.