Which generated components belong in a complete routing world?

Ask for a coherent generated package whose components agree with one another, so your simulator can execute routing decisions without inventing missing business rules.

- Request envelopes with channel-specific metadata, including attachments or referenced forms, so each intake surface supplies the evidence its associated actions expect to receive. - A service catalogue connecting request categories to supported business capabilities, including explicit exclusions that prevent broad queue descriptions from accepting every possible case. - A team directory with queue membership and delegated authority, allowing the simulator to distinguish assigning work to a team from assigning it to an individual. - Relationship tables linking requests to relevant orders, accounts or service locations, with documented cardinality so builders know which associations can coexist legitimately. - Action preconditions describing required evidence and permissions, paired with rejection reasons that explain why an otherwise plausible routing attempt cannot change state. - Terminal state definitions separating completed routing, authorised holding and abandoned work, so the environment does not silently equate every inactive request with success. - A package manifest identifying schema dependencies and required fixtures, enabling loaders to detect missing components before an agent begins interacting with the world.