jevbooks

← All projects

incident-jev

ngpayyappilly/incident-jev

Incident evaluation pipeline where code owns workflow and Jev answers typed questions.

Evaluation & Benchmarking0.99Runner-up: Classification & RoutingScorecard
Automated README summary

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

What it is

A Python service that evaluates incident traces. Code drives the pipeline; Jev is called only for narrow, typed questions, and the final verdict is composed and routed by code.

How it uses Jev

Jev answers probes defined in app/probes.py over facts extracted from the trace. judge.py calls Jev in parallel; decide.py verifies, composes and routes the verdict. Question wording is tuned in the TypeSafe Playground.

Primitives:choicescorenoul

Technique worth stealing

Keep the workflow in code and delegate only narrow, typed questions to the model.

Try it

pip install -r requirements.txt, set TYPESAFE_API_KEY, EVAL_API_KEY, JEV_MODEL, then uvicorn app.main:app --port 8080.

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 projectFound in material0.84
  • Shows a System One patternFound in material0.89
  • Describes handling uncertaintynot found in the excerpt0.05
  • Reports measured numbersnot found in the excerpt0.04
  • Is a runnable toolunclear0.57
  • Top-10 learning shortlist signalunclear0.47
  • Is a replica of the modelnot found in the excerpt0.05
  • Solves a common problem (0–2)score on a 0–2 scale1.33 / 2
  • About JevFound in material0.96
Signals
Jev is core to the project0.84Shows a System One pattern0.89Describes handling uncertainty0.05Reports measured numbers0.04Is a runnable tool0.57Top-10 learning shortlist signal0.47Is a replica of the model0.0500.51Solves a common problem (0–2)1.33 / 2012

no-judgment band (0.40–0.60)

Design patterns
Scorecard0.80Funnel0.50Questionnaire0.42Question bank0.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 6 Oct 2026.