Skip to content
MirrorFirm

Can we scope a useful sample without supplying production records?

A buyer can begin with process descriptions, tool contracts and decision rules, then inspect where a generated sample needs additional operational detail.

**Do we need to provide production records to describe the task?**

A buyer can ask to scope a sample from a process brief. The brief can describe the teams involved, the purpose of the transfer, the decisions the agent may make and the records those decisions depend on. It does not need to start with a bulk export.

**What technical detail is useful?**

Field definitions, permitted tool actions and explanations of common exceptions help establish the required behaviour. Describe constraints in business terms as well as system terms: a field called `release_flag` is less informative than an explanation of who may set it and what action it permits.

**What limits should we expect?**

A brief may omit local conventions, undocumented workarounds or integration quirks. A generated sample based on that brief should be reviewed against the intended process before broader use. Fidelity to unspecified behaviour cannot be assumed.

A useful first step is to provide the process rules you are authorised to share and ask which remaining assumptions the sample would use. Grounding and disclosure risk should still be inspected.

Use a process brief to define the sample while keeping production record transfer outside the starting requirements.

Audience:
Agent developers
Content type:
FAQ
Buyer question:
Scope and getting started

Content release: r-a220eb6e099b243b

More on Cross-team handover