What could a single task in an intake task pack look like?

A task pack for a regional electricity distributor includes the task `TASK-0198`. The starting state holds case `CASE-0412`, a request to connect a new three-phase supply to a light industrial unit. The submission has an address, a requested load and a site plan reference, but no electrical contractor licence number.

The environment exposes four tools: `get_case`, `search_policy`, `request_information` and `route_case`. The policy `RULE-CONN-07` says a connection request above a stated load needs a contractor licence number and a completed load form before it can go to network planning. `RULE-CONN-02` says requests inside a flagged constrained area go to the senior planning queue.

The agent reads the case, finds the address on the constrained list, and sees the missing licence. The reference outcome is that it sends a request for the licence number and load form, sets the status to `awaiting-applicant`, and does not route the case yet. The note must name both missing items and cite `RULE-CONN-07`.

If the agent routes the case straight to senior planning because of the area, the grader records an early routing error: the case reaches planners with gaps they must send back.

**What it teaches:** two rules can both apply, and the order in which they are applied is what the task tests. Completeness comes before routing, and the note must show why.