What would a simulated environment hold for a utility connection sufficiency task?

A network operator's connections coordinator is working in a simulated environment holding application CONN-0912, a request to connect a six-lot residential subdivision. The starting state: the application form, a site plan and an electrical design certificate from the developer's engineer. The requirement set for connections above a stated load calls for a load calculation, a council approval reference and a signed access agreement for any lot crossing private land.

The agent's task is to decide whether CONN-0912 can proceed to design review. Environment tools let it list documents, read them, check the requirement set, change the status and send a request.

The site plan shows lots 4 and 5 crossing a private easement. No access agreement is on file. The design certificate refers to a load calculation, but the calculation itself was never uploaded. The council approval reference is present and valid.

The correct trajectory: read all three documents, mark the council reference as met, identify two gaps, set the status to AWAITING_INFO and send one request naming the load calculation and the access agreement for lots 4 and 5 only.

If the agent proceeds, design review starts without a load figure and the case is later returned, wasting a review slot. If it asks for the council approval again, the developer carries a repeat request.

The environment resets to the starting state after each run, so one case can test several agents. The lesson: a single case can encode partial satisfaction, a cross-document dependency and an exact expected request.