jevbooks

← All projects

typesafe-jev-examples

rajivkuriakose/typesafe-jev-examples

Worked Jev examples: ticket triage and re-ranking, runnable via OpenRouter.

Automated README summary

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

What it is

Starter examples for developers trying TypeSafe's Jev System One model. Includes a ticket-triage example and a re-ranking example, each with sample data and a Makefile, runnable through OpenRouter without an early-access key.

How it uses Jev

In 01, one ticket is state; seven named questions (department Choice, business_impact Score, threatens_churn Noul, etc.) are sent in a single parallel request, and the typed answers drive a routing policy written in code. In 02, each (question, article) pair is its own state with one Noul; calls fan out concurrently and the returned probability is the sort key.

Primitives:choicescorenoul

Technique worth stealing

Pick the primitive by what the answer means, and keep policy thresholds in code rather than in the model.

Try it

git clone, make setup, cp .env.example .env with an OpenRouter key, then make test and make run.

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.95
  • Shows a System One patternFound in material0.61
  • Describes handling uncertaintynot found in the excerpt0.04
  • Reports measured numbersnot found in the excerpt0.22
  • Is a runnable toolFound in material0.62
  • Top-10 learning shortlist signalFound in material0.66
  • Is a replica of the modelnot found in the excerpt0.03
  • Solves a common problem (0–2)score on a 0–2 scale1.02 / 2
  • About JevFound in material0.99
Signals
Jev is core to the project0.95Shows a System One pattern0.61Describes handling uncertainty0.04Reports measured numbers0.22Is a runnable tool0.62Top-10 learning shortlist signal0.66Is a replica of the model0.0300.51Solves a common problem (0–2)1.02 / 2012

no-judgment band (0.40–0.60)

Design patterns
Questionnaire0.98Traffic light0.95Scorecard0.91Question bank0.45Check-up0.3600.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 Sept 2026.