Is adjusting a schedule really a reasoning task, or just arithmetic?

**Is it just arithmetic?**

No. Arithmetic is usually the smallest part. Recomputing instalments after a change is a few lines of code. The harder questions are around it.

**What else does the model have to decide?**

- Whether the requested change is allowed under the product's terms, for example a minimum instalment or a maximum term. - Who has authority to approve it, and whether the requester has supplied what the policy asks for. - Which already-paid or already-delivered items must stay fixed. - How to treat rounding, fees, interest and tax so totals still reconcile. - Which other records need changing, such as a debit mandate, a delivery booking or a customer notice.

**Where do exceptions come in?**

Many requests do not fit the standard path. A customer may ask for a date that falls on a public holiday, a supplier may split a delivery, or a refund may arrive between two instalments. A good task includes cases where the right answer is to escalate or decline rather than act.

**Why is that useful for training?**

It lets a lab separate three skills: reading state, applying policy, and choosing the correct action including no action. Each can be graded on its own. MirrorFirm output is generated, so buyers should inspect how closely the policies and exceptions match the practices they care about.