State and fan-out

state may be a string, a named object, or an array of turns/records. There is no retrieval: omitted fields do not exist. Flavio’s default is an object, with backticked paths in instructions — Does `refund_policy` cover `message` given `order.charges`? Dots and indices are the documented way to point.

Multiple questions on one state are independent and parallel. OmniaKey: B does not see A’s answer; if B depends on A, the dependency lives in your code. TypeSafe’s jaggedness guide: irrelevant detail lowers accuracy — filter state first. Budget: 64K for the request, 32K for state plus the longest question.

The fan-out recipe (systemonemodels): category, refund_requested, has_reproducible_steps, severity in one call. Refund only matters on billing; repro steps only on bugs. Every ticket discards a lane. You pay for parallelism, not for the lanes you keep.

Exercise

Object state: ticket + refund policy. Ask category, refund-wanted, and policy-covers in parallel. On paper: which noul you ignore when category ≠ billing.