J•JEV Field Guide

JEV 101 / THREE LANGUAGES / ONE COMPLETE WORKFLOW

Learn Jev by following one decision from a customer message to a safe action.

A parcel is marked delivered but missing. Which team handles it? Is it urgent? When should a person step in? Start with the worked example, then build your own typed decision.

从“包裹显示送达却没收到”这条工单入手,循序学会 Jev 的 state、Choice / Score / Noul、API 返回值与人工回退。

REAL-WORLD QUESTION / SYNTHETIC EXAMPLE01 → 03

“My parcel says delivered, but nothing arrived. I need it today.”

STATECustomer claim + verified carrier status
QUESTIONSWhich team? · Is it urgent? · What is the tone?
CODERoute, gather facts, or send to human review

Illustration only · No API call on this page

01 / UNDERSTAND

What Jev decides

Learn when a typed judgment helps, and what ordinary code must still own.

Read the introduction
02 / WORK THROUGH

One complete ticket

Trace verified facts, three atomic questions, illustrative answers, six failure cases, and launch checks.

Open the worked example
03 / BUILD

Make a draft

Use a local, no-key lab to create a copyable request and a human fallback plan.

Try the decision lab

START WITH THE REAL QUESTION

Jev returns decisions your code can read. It does not write a customer reply or grant refund permission.

Choice picks from named options. Score rates a defined rubric. Noul reports a statement probability. The guide shows where these results belong in a workflow, how to inspect uncertainty, and what to test before automating any action.

Independent learning site; examples are illustrative and are not results from an API run. Official TypeSafe documentation