What should developers include in a request for a generated sample?

Use this checklist to request a sample that supports a concrete suitability review.

- Describe the late obligation and its business consequence. - Supply the policy assumptions the sample should use. - Name the agent's permitted decisions and actions. - List the systems and record types it must connect. - Identify an exception the team finds difficult. - State the required export and inspection formats. - Nominate who will judge business correctness. - Define the evidence needed to accept the sample.

Keep the request focused on behaviour that matters to the intended agent. A sample dominated by clean, routine reminders may be easy to inspect but provide little evidence about the boundary the team is struggling to automate.

Ask MirrorFirm to make assumptions visible alongside the generated material. If a policy detail is supplied for the sample, reviewers should be able to distinguish that assumption from a requirement the buyer provided.

A useful review ends with a specific finding: the material supports the intended decision, a relationship is missing, or the scope needs revision. That finding gives the next procurement or engineering step a concrete basis.