Which queue-state elements should a generated environment represent?

Ask for these generated queue-state elements when the benchmark needs to test whether an assignment is operationally feasible, and define which elements the agent can inspect before making its decision.

- Queue capability records listing the request categories each team can resolve, including explicit exclusions that prevent a broad category from implying unrestricted authority. - Staff qualification links showing which roles can accept restricted work, with validity conditions that can change eligibility without changing the request itself. - Availability windows that distinguish a closed queue from an open queue with a backlog, since those conditions may require different routing behaviour. - Capacity rules defining whether workload is advisory or a hard assignment limit, so an evaluator can determine when overflow routing is permitted. - Overflow relationships naming eligible fallback queues and the conditions under which each fallback becomes an acceptable destination for the incoming work. - Reservation state showing capacity already committed to pending assignments, preventing the environment from offering the same apparent slot to every competing request. - State freshness metadata indicating when queue information was last updated, with a defined response when an assignment depends on information that has expired.