What should a public sample reveal without undermining a later evaluation?

**What should buyers be able to inspect publicly?**

A sample can show generated request records, destination definitions and a worked routing task. It should reveal enough structure for a technical buyer to assess whether their loader and agent interface can use the material.

**Can that same sample serve as an unseen evaluation?**

Public exposure changes what can reasonably be claimed. A task published on a website, in a downloadable export or through a public MCP server may be retrieved or reused. Its public availability should be visible to customers considering evaluation use.

**What should a reseller request instead?**

Ask for an explicit sample partition and a separately designated evaluation partition, with documented exposure status. Clarify which explanations, expected answers and task identifiers appear through each distribution route.

MirrorFirm could scope those partitions as part of a pilot. Separation alone does not prove that an evaluation is uncontaminated, but it gives the reseller a concrete access design to inspect. The first step is to list every planned public surface and the assets each will expose.