Skip to content
MirrorFirm

What would a generated utility connection case with distractors contain?

A task pack case for a utility connection includes required, optional and decoy documents, so a model must pick out what the policy needs and request the one thing missing.

A task pack case, `CASE-0412`, covers a new electricity connection for a small commercial site. The connections coordinator at a regional utility has the following.

- a completed application form - a site plan - a council approval letter - a copy of a lease - a marketing flyer from the electrical contractor

The policy rule for this connection class requires the form, the site plan and an owner authority. A lease can stand in for the owner authority only if it names the applicant and runs beyond the connection date.

The generated state shows the lease names a different trading entity from the applicant. The council letter is valid but is not on the required list. The flyer is a decoy.

The correct outcome is that the case is not ready. The coordinator moves it to `awaiting-documents` and issues a request for an owner authority, or a lease naming the correct entity. The request explains why the lease supplied does not qualify.

The consequence of proceeding is a scheduled network job against a site where the applicant has no standing, and a cancelled crew booking later.

**What it teaches:** a case set can be crowded with plausible paper. Success depends on matching documents to rule conditions, not on counting pages. A pack can mix required, optional, near-miss and decoy documents so that each failure mode can be separated in scoring.

Decoy documents test whether a model reads the policy or just counts attachments, which is a distinction your customers can measure.

Audience:
Licensed resellers
Content type:
Scenario
Buyer question:
What can be generated

Content release: r-a220eb6e099b243b

More on Document sufficiency