Skip to content

Jev vs OpenJEV

OpenJEV is the same idea as Jev with a chat LLM underneath: score each allowed answer by its log-probability. On a 0.5B backbone it shows what the mechanism alone buys.

Metatext decisions

Three hand-written workflows (support tickets, security incidents, agent traces), seven questions, about 123 judgments per model. Small, so treat a ±0.1 difference as a tie; every question has a majority baseline the model has to beat.

MetricJevOpenJEV
Decision accuracy0.8630.427
Questions over baseline6/73/7
ECE raw → held-out fitted0.0930.210
p50 per case441 ms50 s
Extraction F1n/an/a
Per-question accuracy
TaskQuestionTypeBaselineJevOpenJEV
agent_tracesoutcomechoice0.3570.7860.500
agent_tracesneeds_humannoul0.7140.7140.286
customer_servicedepartmentchoice0.4000.9500.600
customer_servicerefund_requestednoul0.7000.9000.550
customer_servicefrustrationscore0.5000.9500.300
security_incidentsseveritychoice0.3120.8750.500
security_incidentsactively_exploitednoul0.6880.9380.312

typed-decisions

LAYA's public benchmark: four workflows × 100 JSON states × five typed questions = 2,000 decisions. Synthetic; gold is a teacher distribution and the label is its argmax. Large enough to carry an ordering.

MetricJevOpenJEV
Decision accuracy0.726—
Questions over baseline18/20—
ECE raw → held-out fitted0.079 → 0.049—
p50 per case405 ms—

Verdict

Jev, by 0.44 on the Metatext suite. OpenJEV at 0.427 is below every purpose-built encoder and takes about 50 seconds per case on CPU. The row is a scale substitution, not a like-for-like test, but it is enough to say the mechanism is not the advantage.

Related