Docs
OfficialJev Practices & Patterns
Jev 1.13 Jaggedness
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.
- Format
- Docs
- Reading time
- 2 min
- Published by
- TypeSafe AI
- Last verified
- Sep 2026
Highlights
- Counting is unreliable and error grows with size: count in code, one question per item.
- Dates are read as text; extract components with Choice and compare or order them in code.
- Score levels are weak at numeric calibration, so don't interpolate an exact magnitude between levels.
- Structural invariants do not hold: complementary probabilities can sum past 1 and the same question can disagree across primitives.
Quickstart
python
result = client.system_one(
{"items": items},
{
f"item_{i}": Noul(instructions=f"Is `items[{i}]` the name of a fruit?")
for i in range(len(items))
},
)
count = sum(result.nouls[f"item_{i}"].noul > YES for i in range(len(items)))Watch out
The list is reviewed periodically rather than continuously, so treat it as a starting checklist and add the failure modes your own evals find.
Questions about this entry
Short answers drawn from the linked project or page.
Don't ask for a total. The page lists counting as unreliable with error growing with size, and its guardrail is one Noul per item with the sum done in code — the snippet counts per-item booleans rather than trusting a single count answer.
Do it in code. The page says dates are read as text and extracted as components with Choice for comparison outside the model, and warns that Score levels are weak at numeric calibration, so don't interpolate an exact magnitude between levels.
jev-1.13, last reviewed 2026-10-02. Many of the listed edges are expected to be fixed in later versions.
State the exact condition in the instructions and put boundary cases in the criteria, because jev-1.13 answers the words you wrote rather than the intent behind them.
Treat it as a Choice over enumerated parts such as month, day and year, include an explicit not-stated option, then assemble and compare the real date in code.
No. The page notes structural invariants do not hold: complementary probabilities can sum past 1, and the same question can disagree across primitives.
Filter first and send only what the question needs, because irrelevant context distracts the model.
From the Jev guides
Original write-ups on what this entry is for.
From the Jev AI model community
Posts from builders shipping with Jev right now.