Kev has released open local Qwen-based models for making typed probability decisions, giving developers a reproducible alternative to a hosted decision interface. The simultaneous evaluation news is more important than the cloning rhetoric: Jev-like confidence is not a universal property, and published tests show calibration changes sharply with the task.
Key facts
- Kev documents 0.8B, 4B, and 9B models built on Qwen3.5 and released under Apache-2.0.
- The repository supports yes/no, multiple-choice, ordered-score, and isolated multi-question decisions.
- Its README states, “No Jev outputs were used for training.”
- A separate calibration audit reports 44.7% accuracy and 0.325 expected calibration error on a hidden-policy priority task.
Kev does not work like a chatbot that writes a paragraph and then tries to sound confident. The project describes a Qwen base model with a rank-16 LoRA adapter and a pointer head that converts hidden states into probabilities. Its interfaces are noul for yes/no, choice for multiple choice, and score for ordered ratings. This is useful when a machine needs a distribution it can threshold, route, or combine with a business rule rather than prose that a human must interpret. The 9B model card is the relevant model source.
The project calls itself “small Jev-like decision models you can train and run yourself.” That phrase captures the relationship and the limit. Kev is inspired by the typed-decision interface, not evidence that it reproduces a hosted Jev model or its undisclosed corpus and infrastructure. Jared Palmer’s Kev project says, “No Jev outputs were used for training.” That is a welcome, falsifiable-sounding disclosure, but released weights cannot prove a negative about every upstream development artifact. TypeSafe's customer agreement prohibits distillation and training a competing imitation from service output, yet public materials do not establish such a breach here.
The central question is calibration. Accuracy asks whether an answer is right. Calibration asks whether a model that says 70% is right about seven times in ten. It is the difference between a thermometer that occasionally reads the correct temperature and one whose numbers can guide a safety decision. A highly capable model can be dangerously miscalibrated if it is confident exactly where the decisive rule is missing.
Jevals examined Jev and six language models across three public datasets: Banking77 for 77-way choice, HelpSteer2 for a five-level score, and PubMedQA for yes/no. The design used 300 items for each task and five repeated answers per item: seven systems times three tasks times 300 items times five repeats, or 31,500 decisions. Jev was queried through native probabilities, while the general models were prompted to state probability distributions in language. That design choice is a major caveat: verbalized probabilities are not a model's raw token distribution.
The published outcome is mixed. On PubMedQA, Jev and Gemini 3.8 Flash were statistically inseparable under Jevals' ranking procedure; Gemini led Banking77; HelpSteer2 offered weak evidence that any system beat a label-prior baseline. This does not establish that generic language models win overall. It does puncture a simpler marketing narrative in which a specialized decision system has a model-wide calibration advantage.
The separate audit is the sharper warning. Its authors report 3,721 public-benchmark items and 900 synthetic support-ticket items. On an artificial priority task where the decisive organization rule was deliberately absent from the ticket text, Jev had 44.7% accuracy, expected calibration error of 0.325, and average stated probability of 0.74. That is like asking an experienced dispatcher to choose an escalation level without revealing the company's escalation policy: fluent pattern recognition cannot recover a rule that is not there. The audit is small and task-specific, but its source code and raw-response apparatus make it a useful challenge test.
TypeSafe's confidence documentation makes the right practical point: its confidence number is computed from the returned probability distribution and users should establish thresholds on their own data. The strongest counterargument to the audit is that calibration varies by label quality, domain, primitive, and distribution shift; a single synthetic task cannot settle every use case. That is exactly why the result matters. Kev gives developers a local typed-decision tool, but no model card can substitute for calibration testing on the decisions that carry real cost.
Teams should reserve held-out cases, plot reliability against confidence, and choose a threshold according to the false-positive and false-negative consequences of their own workflow.
Originally published on Ground Truth, where every claim is checked against the primary source.
