jevbooks

← All projects

jev-triage

mohammedahmadi1990/jev-triage · Homepage

Benchmarking Java rules, Jev, and Claude Haiku for warehouse goods-receipt triage.

Classification & Routing0.93Runner-up: Evaluation & BenchmarkingCheck-up
Automated README summary

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

What it is

A Spring Boot benchmark comparing a Java keyword rule engine, Jev (TypeSafe AI), and Claude Haiku 5.5 for triaging warehouse goods-receipt remarks, answering category, block, and severity questions.

How it uses Jev

Jev answers three typed questions per remark: category (Choice), whether goods must be blocked (Score), and severity (Choice). The probabilities returned are used to compute accuracy, calibration, and tuned block thresholds in the analysis.

Primitives:choicescore

Technique worth stealing

Using a decision model with typed answers and probabilities instead of free-text LLM output for structured triage.

Try it

Run the Spring Boot app and benchmark, then analyze results with python analysis/analyze.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.13.0
Project signals
jev-1.13.0
Category
jev-1.13.0
Pattern tags
jev-1.13.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.15
  • Shows a System One patternFound in material0.64
  • Describes handling uncertaintynot found in the excerpt0.08
  • Reports measured numbersnot found in the excerpt0.12
  • Is a runnable toolnot found in the excerpt0.10
  • Top-10 learning shortlist signalunclear0.45
  • Is a replica of the modelnot found in the excerpt0.07
  • Solves a common problem (0–2)score on a 0–2 scale0.99 / 2
  • About JevFound in material0.98
Signals
Jev is core to the project0.15Shows a System One pattern0.64Describes handling uncertainty0.08Reports measured numbers0.12Is a runnable tool0.10Top-10 learning shortlist signal0.45Is a replica of the model0.0700.51Solves a common problem (0–2)0.99 / 2012

no-judgment band (0.40–0.60)

Design patterns
Check-up0.76Flight recorder0.49Questionnaire0.43Traffic light0.3100.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 18 Oct 2026.