What should the environment state for a sufficiency task include?

A task is only checkable if the starting state and the expected end state are both written down, so cover these items.

- A case record with the attributes that decide which requirements apply, plus its opening status and clock state. - A requirement table with conditions, accepted document types, validity windows and any rule that allows substitution. - Documents attached to the case, each with type, named party, issue date, signed flag and generated content text. - Held records the business already has, such as a customer profile or prior approval, that can satisfy a requirement. - A scripted event schedule for customer replies, including partial replies and silence past a deadline. - A tool list with argument schemas and the state changes each valid call is allowed to make. - An answer key listing missing items, correct action, end status and clock state for each case. - A reset point and seed so the same starting state can be restored exactly for every run.