Skip to content
MirrorFirm

Can a task pack include overlapping or changing routing policies?

A task pack can include policy versions, exceptions and precedence rules so agents must determine which instruction governs a particular request.

**Can a pack include more than one routing policy?**

Yes. A generated pack could contain a general intake policy, a product-specific exception and a temporary operational instruction. Each policy can have an identifier, scope, effective dates and a stated precedence relationship.

**What would the agent need to decide?**

A utilities request may normally belong to account services, while an active incident instruction directs requests about a particular service interruption to an incident queue. The agent must establish whether the incident instruction covers the request's location and time before applying the exception.

**Should conflicts always have a hidden correct answer?**

No. A task can deliberately present unresolved policy conflict. In that case, the expected action can be escalation to a policy owner, with the conflicting provisions identified. Inventing a precedence rule should not receive credit.

**What should a buyer request?**

Ask for machine-readable policy metadata alongside readable policy text, plus an explanation of how expected actions were derived. This allows developers to distinguish policy retrieval failures, scope interpretation errors and unsupported decisions when reviewing an agent's behaviour.

Expose policy interpretation explicitly instead of hiding it inside unexplained destination labels.

Audience:
Agent developers
Content type:
FAQ
Buyer question:
What can be generated

Content release: r-a220eb6e099b243b

More on Service routing