State is the data half of a System One request. The other half is the set of typed questions you attach to it. Jev accepts text only, passed as a string or as structured text (a JSON object or an array of text values). No image, audio or video input. Total context is 64k tokens per request, and state plus the longest single question is capped at 32k tokens.
TypeSafe’s build guidance is blunt about what belongs in there: “Include only the context relevant to the current questions. This helps the model avoid distractions and context rot.” That advice has teeth. The published jaggedness page for jev-1.13 lists large state full of irrelevant detail as a documented failure mode, where unrelated content acts as a distractor.
A practical version: for support triage, pass the customer message and the last two replies, not the full account history and every past ticket. Then ask narrow questions against that trimmed state.
The decomposition rules are covered in how to build with System One models, and what you attach to state is covered in the question entry. Token limits and pricing sit on the Jev model page.