How should I scope a set-up environment or task pack?

Scoping a set-up environment starts with three choices: the domain, the depth of the workflow and the interface you will run it through.

**Domain.** Pick one where your agent will actually be used, such as retail banking onboarding, policy issue, utility connection or client engagement set-up. Starting with one avoids vocabulary that is only half right in each.

**Depth.** Decide how far set-up runs. A shallow scope stops at account creation. A deeper one includes obligations, a handover to a second role, and a later event such as a first invoice or claim that exposes earlier mistakes.

**Interface.** Say whether you want files you load into your own simulator, a task pack that targets your tool definitions, or a simulated environment with its own tool interface. Each carries different effort on your side.

Then set the limits you care about: how many distinct tasks, how many seeded exceptions per task, and which fields must appear. Licensing terms, delivery arrangements and any volume or timing commitments are agreed with MirrorFirm directly; do not assume them from this page.

Be clear about what the material is. It is generated and synthetic, informed by direct observation of how businesses operate. It is not real business records, and it does not come with guarantees about privacy or regulatory outcomes. A short pilot lets you inspect it before you commit to more.