What should a simulated schedule environment include?

When you ask for a simulated environment, name each of these so scope is clear before generation starts.

- **Seeded state:** accounts, agreements, schedules, instalments, mandates and approvals, with stable identifiers such as `SCH-3310`. - **Policy store:** versioned documents the agent can search, including superseded versions that should not be applied. - **Tool actions:** read schedule, propose change, submit for approval, cancel mandate, send notice, add note, escalate case. - **Clock control:** a simulated date so tasks involving due dates, cut-offs and holidays are repeatable. - **Role model:** which actor may take which action, so authority limits are enforced by the environment and not left to the prompt. - **Deterministic reset:** a seed and snapshot that return the environment to the same start state between runs. - **Event log:** every tool call and state change recorded, so graders can check order as well as outcome. - **Variation controls:** domain, amounts, term lengths and exception rates that can be changed without rewriting tasks.

Not every item is needed for a first pilot. A reasonable start is seeded state, policies, tools and reset, with the rest added once the first results show where the gaps are.