jevbooks

← All projects

jev-as-judge

patchy631/jev-as-judge

Auditable refund-support trace evaluation with Jev and Opik.

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

A tutorial that replays ten synthetic frozen support traces through deterministic checks and Jev semantic evaluation, then records results as an Opik experiment. For evaluators learning to build auditable LLM-judge pipelines.

How it uses Jev

Jev answers three yes/no criteria (grounded, addresses_request, action_honest) and one ordered helpfulness rubric in a single request over the request, policy, tool results, and final answer. Probabilities map to Opik metrics via a custom BaseMetric; failures are marked judge_error, not scored.

Primitives:choicescorenoul

Technique worth stealing

Run deterministic checks before paying for semantic evaluation, and keep raw answers, resolved model id, and rubric version for audit.

Try it

python -m jev_judge.cli --mode demo (offline); live mode needs TYPESAFE_API_KEY.

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 projectFound in material0.88
  • Shows a System One patternFound in material0.76
  • Describes handling uncertaintynot found in the excerpt0.04
  • Reports measured numbersnot found in the excerpt0.05
  • Is a runnable toolnot found in the excerpt0.15
  • Top-10 learning shortlist signalFound in material0.74
  • Is a replica of the modelnot found in the excerpt0.04
  • Solves a common problem (0–2)score on a 0–2 scale0.85 / 2
  • About JevFound in material0.99
Signals
Jev is core to the project0.88Shows a System One pattern0.76Describes handling uncertainty0.04Reports measured numbers0.05Is a runnable tool0.15Top-10 learning shortlist signal0.74Is a replica of the model0.0400.51Solves a common problem (0–2)0.85 / 2012

no-judgment band (0.40–0.60)

Design patterns
Funnel0.98Questionnaire0.97Fail open, fail closed0.94Traffic light0.88Scorecard0.81Flight recorder0.54Grey zone0.51Blind review0.49Question bank0.44Inspection0.2000.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.