Put shared facts and rules in state. Add one question for each check.
For a support ticket, you might ask which team owns it, whether required evidence is present, and how much impact the issue has.
Each question uses the same input. Questions do not receive each other’s answers. If one decision depends on another, make a second request with the first result included in state.
Use explicit field names in instructions, such as “Read ticket and apply policy.” These paths are prompt text, not a query language.
One request saves client round trips. It does not guarantee constant latency or shared token cost. More questions can take longer to evaluate.