jevbooks

← All projects

jev-vs-spacy

oluies/jev-vs-spacy

Braintrust bake-off: spaCy vs TypeSafe Jev on spam and routing.

Classification & Routing0.96Runner-up: Evaluation & BenchmarkingFunnel
Automated README summary

Automatically summarized from the README on 22 Oct 2026; not a run by jevbooks. Run instructions and author-reported outcomes still need verification.

What it is

An eval that runs spaCy textcat, TypeSafe Jev, Laya and Claude on the same email tasks (Enron spam, Bitext support routing, Swedish MASSIVE scenarios) with identical test rows and deterministic scorers, logged to Braintrust.

How it uses Jev

Jev is asked typed questions zero-shot about each email's state; its per-option probabilities and confidence are recorded as per-row metadata and scored against gold labels. Low-confidence answers are framed as a review policy. The README does not show the exact question-building code.

Primitives:choicescorenoul

Technique worth stealing

Tune category descriptions on the dev split only, then score the test set once.

Try it

uv sync; uv run python data.py; export TYPESAFE_API_KEY=...; uv run python eval_email.py

View on GitHub

Start using Jev: API key and your first request →

Model judgments from README excerpts

Project signals use repository metadata, an existing summary and the first 700 README characters, not the full project. “Not found” means not detected in that material; it does not establish absence. These are the original judgments with recorded models and dates, not source audits or run results.

Models & evaluation dates

Inclusion gate
jev-1.14.0
Project signals
jev-1.14.0
Category
jev-1.14.0
Pattern tags
jev-1.14.0

Evidence

These signals use repository metadata, an existing summary and at most 700 cleaned README characters. ≥ 0.60 means reported in that excerpt; ≤ 0.40 means not found there. The middle band is inconclusive. None is a source-code audit or a test result. The runnable-tool question excludes research experiments; the recommendation question asks for a learning shortlist, not a quality verdict.

  • Jev is core to the projectnot found in the excerpt0.09
  • Shows a System One patternnot found in the excerpt0.13
  • Describes handling uncertaintynot found in the excerpt0.02
  • Reports measured numbersnot found in the excerpt0.04
  • Is a runnable toolnot found in the excerpt0.08
  • Top-10 learning shortlist signalnot found in the excerpt0.15
  • Is a replica of the modelnot found in the excerpt0.03
  • Solves a common problem (0–2)score on a 0–2 scale1.74 / 2
  • About JevFound in material0.99
Signals
Jev is core to the project0.09Shows a System One pattern0.13Describes handling uncertainty0.02Reports measured numbers0.04Is a runnable tool0.08Top-10 learning shortlist signal0.15Is a replica of the model0.0300.51Solves a common problem (0–2)1.74 / 2012

no-judgment band (0.40–0.60)

Design patterns
Funnel0.71Check-up0.59Traffic light0.33Questionnaire0.31Blind review0.27Question bank0.25Grey zone0.24Prefetch0.2200.51

no-judgment band (0.40–0.60)

The Jev model and date for each judgment stage are listed above. Card written by DeepSeek V4.1 Flash from the README on 22 Oct 2026.