Why must an agent understand which accounts belong in a scheduled review?

**Isn't the review population just a list supplied to the agent?**

Sometimes it is, but an agent may also be responsible for constructing or checking that list. In a utility operation, a scheduled review of payment arrangements might include active arrangements due for reassessment while excluding arrangements already replaced by a new agreement.

**Why does that matter for training?**

A record can satisfy a simple date filter yet fall outside the intended population. A superseded arrangement may retain its old review date. Conversely, an active arrangement transferred between account records may disappear from a query that assumes the original account remains authoritative.

**What should a generated task teach?**

It could require the agent to apply an explicit population rule, resolve replacement links and explain exclusions. The output would include both the selected records and reasons for leaving other candidates out.

**What business failure does this reveal?**

An agent can produce excellent assessments for every record it opens while missing eligible customers entirely. Population-level reasoning makes that omission visible and tests whether the agent understands the boundary of its responsibility.