Vibeleaderboard
Index / tool
Visit github.com
Category
Developer Tools
Rank

Previous survey · No. 827 ·

Pricing
Open Source
Type
TOOL
Use case
Models: Train & Run
Interfaces
API
Latest release
kev-1.0
Date

About

Kev is a family of small decision models (0.8B, 4B, and 9B parameters) built on Qwen3.5, designed to be trained and run locally rather than through a hosted service. It answers yes/no, multiple-choice, and rating questions in a single request over shared input text, and exposes an API compatible with TypeSafe's System One SDK so existing clients can point at a self-hosted server.

What it does

Kev reads one document plus a set of typed questions about it and returns a probability for every option you supplied, without writing any text. The document is processed once and cached, then each question continues from it separately, so answers never influence each other. Under the hood a Qwen backbone runs in prefill-only mode and a small pointer head scores each option. A fitted temperature ships with each checkpoint, so the numbers are meant to be thresholded: automate the confident cases, send the rest to a person.

Why it's ranked here

The headline claim is measured, not asserted. On datasets Kev never trained on, the largest size reaches 0.851 development accuracy against 0.857 for Jev, the hosted model it imitates, and the authors say plainly this is not a controlled comparison. Every number traces to a committed report, test sets are read once per released model, and the release notes list known weaknesses by name. Apache 2.0 throughout, with checksummed checkpoints and pinned weight revisions. That level of evaluation discipline is rare for a one-person model project.

What's good

Answers are distributions, not labels. The quick start ticket mentions a return, a late delivery and a double charge, and the department probabilities split 0.47, 0.28 and 0.25 accordingly. The release removed a silent failure: a document over 65,536 tokens is now refused with an error naming the count, rather than cut. Each model card states a validated context, the longest document where contract accuracy stays within 3 points of the 8k result. Fine-tuning is documented with honest numbers, including that 400 records gave a gain inside the noise.

Tradeoffs

The three smaller sizes trained on documents of at most 7,552 tokens and are validated only to 8,192, even though the server accepts eight times that. On datasets no Kev saw, the smaller sizes sit 13 to 31 index points below Jev. Date arithmetic is weak below the largest size, at 0.35 to 0.725 against Jev's 0.95. The 0.8B model's tool-call routing accuracy fell to 0.133, below chance. The largest model is overconfident on long contracts. The package declares itself alpha, and the 9B and 27B Mac paths are expected but not measured.

How to use it well

Start with the 4B size on a 24 GB GPU or a 32 GB Apple Silicon Mac, keep documents under roughly 8,000 tokens, and freeze confidence thresholds on a labelled sample of your own traffic. It fits classification, routing, triage and policy checks where you want to send uncertain cases to review. If you already call Jev through the TypeSafe Python client, swap the base URL. Turn on the date preprocessor for deadline questions. It does not generate, summarise or chat, it is English only, and it is not for unreviewed decisions with legal or medical consequences.

Technical notes+

kev/api.py maps all three question types onto one pointer primitive: yes/no becomes two options, choice takes 1 to 255 named options (MAX_OPTIONS = 255), score returns the expected level index. Confidence formulas mirror TypeSafe's reference adapter, and round_prob keeps 4 decimals so a 255-option distribution stays within TypeSafe's sum tolerance. date_facts appends deterministic day counts between every pair of dates. kev/benchmark.py scores a local checkpoint or any System One endpoint via --remote, validating probability keys and sums. docs/model-cards/kev-4b.md describes a frozen 32-layer backbone (24 Gated DeltaNet, 8 full attention) with a rank-16 LoRA adapter of 33.8M parameters. pyproject.toml pins torch below 2.9 and requires Python below 3.14.

Observed

License
Apache-2.0 (code, adapters and heads; Qwen base models also Apache-2.0)
Language
Python, requires 3.12 or 3.13
Packaging
uv project installed from a git clone, optional serve and mlx extras; weights on Hugging Face Hub
Interfaces
HTTP endpoint compatible with TypeSafe System One; TypeSafe Python SDK; benchmark CLI module
Platform support
CUDA and ROCm GPUs; Apple Silicon through MLX
Model sizes
0.8B, 4B and 9B LoRA adapters; 27B full weights
Declared maturity
Development Status 3 - Alpha classifier in the package manifest
Tests
pytest configured with a tests directory and a server marker for live-endpoint tests

Read from README.md, pyproject.toml, LICENSE, PLAN.md, docs/releases/kev-1.0.md, docs/model-cards/kev-4b.md, kev/api.py, kev/benchmark.py, docs/autoresearch.md.

Tags

decision-modelsqwenllmopen-sourceclassificationself-hosted

Tech Stack

Python

Comments (0)

No comments yet

Editorially curated, with community endorsements as a secondary signal. Corrections welcome.