Jev directory
CommunityJev Benchmarks & Evaluations
Jev Study
Portuguese-language technical study of Jev, TypeSafe AI's System One decision model, benchmarked against a structured-output LLM baseline. Ships a Python 3.11 harness, a 45-task synthetic eval set, and a runner that records decisions, confidence, latency, tokens, and estimated cost.
- Stars
- 0
- Reading time
- 2 min
- Published by
- Community
- Added
- Nov 2026
Highlights
- Python 3.11+ project using uv, Ruff, and pytest; CI runs lint and tests without TypeSafe or LLM keys.
- Gabarito v1 holds 45 synthetic tasks, 15 each of Choice, Score, and Noul; six items are written as low_confidence.
- JevHttpBackend calls POST /v1/systemone through the standard library and refuses redirects so the Authorization header stays on host.
- Runner records backend, requested and responding model, decision, confidence, probability, latency, tokens, and estimated cost.
- No model results are published in the repository; the calibration claim stays a hypothesis until a live run.
Questions about this entry
Short answers drawn from the linked project or page.
The project uses uv. Running uv run jev-study executes the fifteen placeholder tasks, while the evaluate-jev command reads the v1 gabarito in data/eval/decisions.v1.jsonl and runs either the echo backend or the live adapters.
No key is needed for CI or the local echo run. A live Jev run needs a TypeSafe key for JevHttpBackend, and the LLM baseline needs an OpenAI key, since the openai package is only imported during a live call.
Only synthetic tasks written inside the repository, in Portuguese with English keys. No customer data is included. The single Box task is a placeholder that the runner skips because it has no image asset or danger-zone header.
Three things on the same labeled tasks: whether the response obeys the typed schema (Choice, Score, Noul, Box), whether the decision agrees with the gabarito, and whether declared confidence tracks correctness.
Choice is scored by equality of the chosen key, Score by the nearest whole rubric level, and Noul by a 0.5 threshold where a probability of 0.5 or higher counts as yes. Invalid response types and transport errors leave the match null.
The client posts to /v1/systemone using either the jev-latest alias or a versioned id, currently jev-1.14.0. The client requires the usage field because the API marks it as mandatory.
It publishes no model results, covers no Box cases, and uses a small synthetic set of 45 tasks. It is a harness and methodology, not a production benchmark or a measurement of speed, cost, or hallucination rates.
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.