jevbooks

← All projects

jev-apps

mani-bellan/jev-apps

Pipeline failure triage and customer support router built on Jev.

Automated README summary

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

What it is

Four small Python apps for developers: triage failed data-pipeline tasks, route customer messages to specialist agents, score agent-run steps (Agent EKG), and check suspicious messages for scams (Scam Shield).

How it uses Jev

Triage: one Jev call per failed task returns a root-cause choice and an impact score; triage() maps these to review, retry, page, or ticket. Router: one Jev call returns per-agent yes/no probabilities plus urgency; agents with probability ≥ 0.5 reply, and a human handles no-match or urgency ≥ 0.7.

Primitives:choicescore

Technique worth stealing

Combine a choice (root cause) and a score (impact) in one Jev call, then map the answers to a single action with explicit thresholds.

Try it

Set TYPESAFE_API_KEY, then run `uv run triage.py samples/*.json samples/dbt/*.json` or `uv run main.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 projectFound in material0.92
  • Shows a System One patternFound in material0.66
  • Describes handling uncertaintynot found in the excerpt0.07
  • Reports measured numbersnot found in the excerpt0.10
  • Is a runnable toolFound in material0.78
  • Top-10 learning shortlist signalunclear0.51
  • Is a replica of the modelnot found in the excerpt0.04
  • Solves a common problem (0–2)score on a 0–2 scale1.94 / 2
  • About JevFound in material0.98
Signals
Jev is core to the project0.92Shows a System One pattern0.66Describes handling uncertainty0.07Reports measured numbers0.10Is a runnable tool0.78Top-10 learning shortlist signal0.51Is a replica of the model0.0400.51Solves a common problem (0–2)1.94 / 2012

no-judgment band (0.40–0.60)

Design patterns
Traffic light0.88Scorecard0.85Funnel0.56Questionnaire0.55Flight recorder0.30Blind review0.2700.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 20 Oct 2026.