What should a generated environment let an overdue-handling agent do?

Use this checklist to define the action surface of a generated overdue-handling environment.

- Read the outstanding obligation and linked evidence. - Retrieve the applicable contact permissions. - Draft a follow-up for review. - Submit an authorised contact action. - Assign a resolution task to an eligible role. - Apply a supported hold or escalation reason. - Inspect the result of each attempted operation.

Each action should have preconditions and effects. A draft operation may create a reviewable message without changing the contact history. A submit operation may require approval and then create a delivery attempt. Assigning a task should change responsibility only if the receiving role is eligible under the environment's rules.

MirrorFirm could generate tool definitions, permission fixtures and response payloads around these operations. The scope can also include denied actions, such as an agent attempting to remove a hold that requires supervisor approval.

Developers should identify which consequences the environment actually simulates. If delivery is represented only as an accepted queue entry, the agent must not interpret that response as confirmation that the recipient read or acted on the message.