Can a task pack contain changes that should remain unresolved?

**Can a generated pack include a request with no single executable interpretation?**

Yes. A logistics customer writes, “Use the depot address from next time.” The customer has several recurring consignments and two depot contacts. The words do not identify which depot or whether the instruction applies to every consignment.

**What records make that ambiguity useful?**

A release can contain the message, recurring shipment templates, contact locations and previous instructions. It can also contain an ambiguity annotation identifying the unresolved dimensions. The annotation should describe what information is missing without inventing an answer the customer never supplied.

**What can the expected response contain?**

A task pack could accept a clarification that names the relevant alternatives and leaves operational records unchanged. An interactive variant can provide a generated customer reply after a suitable question, allowing the task to continue from uncertainty to execution.

For resellers, label these cases as clarification tasks rather than incomplete data. Keep the clarification target separate from any later customer reply so downstream buyers can choose between single-turn evaluation and conversational training. This gives unresolved intent a deliberate role in the product instead of treating it as a packaging defect.