Why license handover tasks instead of ordinary departmental task data?

**What do handover tasks add to ordinary departmental data?**

They expose situations where one team's work is valid but the next team's work cannot begin. A model must reason about how local completion affects the wider process, rather than simply classify a record as finished.

**What does that look like in utilities operations?**

A field coordinator marks meter work complete after receiving a technician's completion report. Billing still needs a validated opening reading and an effective date. The field task can be complete while the billing transition remains blocked. Treating those states as contradictory would be a reasoning error.

**Why does this matter to a reseller?**

It creates a distinct licensing proposition for customers building agents that operate across business functions. Generated tasks could assess whether an agent recognises an unsatisfied dependency without incorrectly reopening completed work or authorising premature billing.

**What should the catalogue make explicit?**

Describe which teams, completion conditions and downstream prerequisites are represented. A task that checks readiness between field operations and billing should not be presented as evidence that a model understands every utility workflow. The licensed scope should match the dependency reasoning actually exercised.