Skip to content

Jev glossary

Core Concepts

State

The content a request asks Jev to evaluate: a string, a named object, or an array of messages, shared by every question in the request.
Category
Core Concepts
Also known as
—
Reading time
1 min
Related terms
5
Directory entries
3
Docs
docs.typesafe.ai
Added
2026-09-24

Definition

State is the material you would present to a panel of experts before asking for a judgment: a support message, a passage, a conversation, a record, or the current state of your application. It can be a plain string, a JSON object with named fields, or an array of text values.

One request pairs one state with one or more questions. Every question sees the same state and is evaluated independently. Objects are recommended for most requests, and trimming state to what the questions need is part of the craft because unrelated detail causes context rot.

Tagscoreapi

From the Jev directory

Directory entries that go deeper on this term.

How to shape what Jev evaluates: a string, a named object, or an array of messages. Every question in a request sees the same state and is evaluated independently.
Jev Practices & PatternsDocs#official#docs#state
Official
The raw HTTP contract behind every SDK: POST a state plus typed noul, choice, and score questions to /v1/systemone, and get one answer per question, with error codes and retry guidance.
Jev Guides & ArticlesDocs#official#docs#api
Official
A maintained list of jev-1.13's known failure modes, literal reading, unreliable counting, dates as text, indirection, context rot, and contradictory criteria, each with a guardrail.
Jev Practices & PatternsDocs#official#docs#evaluation
Official

From the Jev AI model community

Posts from builders shipping with Jev right now.

Follow @typesafeai