JEV FIELD MANUAL

Jev 101 — decisions for software, not chat

Unofficial Guides + Use Cases for TypeSafe’s System One / Jev. Facts from public docs. Not affiliated with TypeSafe.

  • Guides + Use Cases + Ecosystem + FAQ
  • Choice · Score · Noul for software decisions
  • Recipes: routing · RAG · n8n · extract
  • indexed · 62 use-case outlines

Guides · foundations

What Jev is → vs chat models & code → Choice / Score / Noul → first small task.

01

What is Jev?

Jev is TypeSafe’s System One decision model: send state + typed questions, get structured answers your code can branch on—illustrated with a support email, not a chat.

  • Paraphrased from public TypeSafe docs
  • See Sources below

02

Jev, chat models, and code — who owns what

Code owns control flow and side effects; Jev owns narrow semantic judgments; LLMs write prose when you need text. Prefer workflows + gates over open agent loops.

  • Paraphrased from TypeSafe how-to-build guidance
  • See Sources below

03

Choice, Score, or Noul — how to pick

Choice selects from a closed set; Score rates ordered levels; Noul returns P(yes). Mix them in one call; each question runs in parallel against the same state.

  • Paraphrased from public primitives docs
  • See Sources below

04

Pick a small first task

Shrink “AI handles support” to a reviewable label on desensitized mail. Define input, options, success checks, and what you refuse to automate.

  • Field-manual template; not an official mandate
  • Cite TypeSafe use-case map for patterns

Use Cases

Catalog of decision shapes — who, steps, expected effect, sources. Not chatbots.

All use cases (62)

Ecosystem

TypeSafe + Gateway (official paths) and independent demos with clear boundaries.

Ecosystem (5)

official

TypeSafe Jev (official)

Official TypeSafe Jev: docs, playground, console API keys, Python/JS SDKs. Returns structured Choice / Score / Noul answers — not chat.

integration

Vercel AI Gateway

Call Jev through Vercel AI Gateway (`typesafe-ai/jev`) with the AI SDK evaluate path. Useful when you already route models through Gateway.

community

SemIf (formerly OpenJev)

SemIf reproduces a Jev-style interface on open models. It is independent and does not reproduce TypeSafe training or hosted Jev accuracy. Never cite SemIf numbers as “Jev accuracy.”

community

typesafe-computer-use

Community demo that pairs perception with decision-style calls. Independent project — not an official TypeSafe product.

community

Unclutter

Independent extension demo in the broader Jev-adjacent ecosystem. Not affiliated with TypeSafe.

Guides · recipes

Prepare materials → support routing → RAG filtering → n8n → extract and validate.

All Guides (35)

hands-on

Atomic questions beat crammed principles (Takuma Yoshida)

External note.com write-up by Takuma Yoshida (2026-10-29): on Kaggle Game Arena Bargaining, splitting negotiation principles into many small hosted TypeSafe Jev questions (then optionally moving calculable parts to Python) beat stuffing seven principles into one prompt.

hands-on

Jev Gives You Probabilities, Not Decisions (Olivier Miossec)

External DEV write-up by Olivier Miossec (posted 2026-10-09, edited 2026-10-25): the mental model behind hosted TypeSafe Jev—state vs questions, Score / Noul / Choice, confidence thresholds, and writing atomic questions—with PowerShell examples that apply in any language.

hands-on

Jev in Cloud Operations with PowerShell (Olivier Miossec)

External DEV write-up by Olivier Miossec (2026-10-01): use Doug Finke's Jev PowerShell module to gate Bicep What-If changes, review NSG rules, and triage Azure Policy linter findings with hosted TypeSafe Choice / Noul / Score questions.

SYSTEM ONE

Build with System One

Code owns control flow; Jev owns narrow semantic judgments; LLMs write prose when you need it.

Read Jev vs LLM →

FAQ

Is Jev an LLM? What is Noul? OpenJev ≠ Jev. Confidence misuse.

Open FAQ (8)

Repeating launch-blog multiples as independent Jev 101 benchmarks.

About 193× / 444× speed-cost claims

Those figures are TypeSafe workflow-eval marketing on their launch blog—we do not re-run them here.

HTTP 401 Unauthorized from TypeSafe API or Gateway when calling System One / jev.

API returns 401

Unauthorized usually means missing/invalid TYPESAFE_API_KEY, wrong auth header, or calling the wrong host.

Treating every Choice/Score as infallible automation fuel.

Can Jev be wrong?

Yes. Use confidence paths, human escalation, and domain evals. Honest uncertainty is a feature.