Jev glossary
PrimitivesDot-and-index path
Backtick path reference
Naming a state field inside instructions with backticked dot-and-index paths, such as `ticket.messages[0].text`.
- Category
- Primitives
- Also known as
- Dot-and-index path
- Reading time
- 1 min
- Related terms
- 4
- Directory entries
- 2
- Docs
- docs.typesafe.ai
- Added
- 2026-09-24
Definition
When a question is about one part of a structured state, the docs recommend naming it in the instructions with a backticked path. The model then knows which part of the state to judge, and readers can see it too.
Explicit paths reduce ambiguity and indirection, which are two documented accuracy risks. The same convention is used to refer to data fields embedded in structured instructions.
Tagsprimitivesdesign
Related terms
Definitions that connect to this one.
StateThe content a request asks Jev to evaluate: a string, a named object, or an array of messages, shared by every question in the request.Core ConceptsInstructionsThe field that states what a question should judge; accepts a string, an object, or an array for extra structure.PrimitivesStructured instructionsPutting the question in one field and its supporting data, examples, or focus notes in others instead of one long string.PrimitivesIndirectionQuestions about a property of a property, or with double negatives, cost accuracy; write instructions as directly as possible.Evaluation & Training
From the Jev directory
Directory entries that go deeper on this term.
The three TypeSafe question types, the typed answers they return, how to choose between them, and how to ask several in a single call.
Jev Practices & PatternsDocs#official#primitives#choice
Official
Instructions, option descriptions, score levels, and noul criteria all accept JSON, so you can label question parts, pass schemas and taxonomies, and keep candidate paths alive.
Jev Practices & PatternsDocs#official#primitives#architecture
Official
From the Jev AI model community
Posts from builders shipping with Jev right now.