How should an environment team scope a first schedule pilot?

The most useful first step is a small, well-defined slice that you can load and test, rather than a broad request.

**Pick one domain variant.** An instalment plan on a loan, an arrears arrangement at a utility and a staged delivery run share structure but differ in vocabulary, rules and fields. Choose the one closest to the agents you are building.

**Limit the action surface.** Name the tools you will expose, for example read, add payment, defer and split. Add cancel and waive later.

**Bound the policy set.** Start with a few rules whose correct outcomes are clear, plus a small number of deliberate edge cases.

**State the purpose.** Evaluation packs need held-out tasks and stable graders. Training sets need variety and many starting states. The two can be scoped separately.

**Define what good looks like.** Write down the invariants, expected end states and escalation rules you want the pilot to test.

Details such as volume, format, cadence and cost are matters to agree with MirrorFirm for the engagement, and nothing here sets them.

Keep in mind that the material is generated. Include in the scope a review of grounding and disclosure risk, so that it is part of the pilot and not left until later.