Jev-Style 2B Decision v3 GGUF
The v3 Jev-Style decision model at 2B in GGUF: F16 3.78 GB and Q8_0 2.01 GB match PyTorch FP32 on 100% and 99.7% of parity rows, 73.6% on JevBench v1.4.1 public items.
- Published by
- Community
- Author
- chaoliangUNSW
- Last verified
- Oct 2026
- Languages
- Python
- Capabilities
- Open sourceSelf-hostedRuns locally
Highlights
- Three files built with unmodified llama.cpp at commit 441df11f: F16 3.78 GB, Q8_0 2.01 GB and Q4_K_M 1.27 GB.
- F16 is 100% top-1 identical to PyTorch FP32 and Q8_0 99.7%; Q4_K_M holds 95.7% with a 0.346 maximum probability delta.
- 73.6% on JevBench v1.4.1 public items, the highest among Qwen3.5-2B-family systems on the board, with 95% CI 67.6-78.9%.
- 25,600 tokens per call with no option cap; questions and options over 2,048 tokens go through a numbered-option catalogue, nothing truncated.
- Reads a 24,501-token state once: the first question takes 16.2 s and a further question about the same state 0.17 s.
Watch out
The bundled jev-score-v2 scorer must be built once from build_jev_score.sh, and the jev-style package 0.3.0 or later is required. The 73.6% is self-run with the official harness rather than a board entry, and for long documents the card says to use Q8_0 or F16 because Q4_K_M is noticeably noisier.
Questions about this entry
Reactions & coverage
Posts, threads, and videos about this entry from around the web.
Hacker News: ASTGL replay chose local Laya routing over hosted Jev on one Mac Studio setup.
Jmeg8r15 pointsDoes an open-weight decision model beat a hosted one? Jev vs. LayaRead the thread on Hacker NewsReddit: A walkthrough of routing between models with Jev.
Facebook: Intake Router keeps diagnosis out of the answer space at the front desk.
FacebookClinicnotes
LinkedIn: What multimodal decision models actually change, and what they do not.
LinkedInJevDirectory.org
More Jev resources like this
From the Jev guides
Original write-ups on what this entry is for.
From the Jev community
Posts from builders shipping with Jev right now.