Can generated routing tasks include missing information and customer replies?

**Can a request begin without enough information to route?**

Yes. A generated professional services request can ask for an account change without identifying whether it concerns billing access or access to a project workspace. Both destinations remain plausible until the missing distinction is resolved.

**What can the package contain beyond the opening message?**

It could include a missing-fact model, approved clarification intents and response branches. Asking which account function is affected can reveal the necessary fact. Asking the requester to choose an internal department may provide no reliable information because the requester does not know the organisation’s structure.

**Must replies be generated freely at runtime?**

No. A builder can request fixed response branches for reproducible tests or a constrained respondent model for broader interaction. The scope should specify what facts the respondent knows and when it can decline to answer.

**What state changes follow a clarification?**

The environment can add an evidence record, mark the information gap as resolved and enable previously unavailable destinations. MirrorFirm could generate these dependencies so that asking a useful question has an observable effect on the available routing actions.