AI research · Plain-language guide
What are Jev, AUROC, and RLCD?
A simple guide to a paper about using one AI model to check another AI model’s responses—and what its results do and don’t tell us.
Imagine an AI answers a user’s request. Did it give dangerous advice? Did it simply agree with a mistaken claim? Did it make something up? Researchers need ways to check for these kinds of failures. In the paper “Just Ask Jev”, they test whether Jev, a decision-focused AI model, can help.
What does Jev do?
Jev is given a conversation and a specific question, such as: “Does this answer provide harmful help?” It returns a score, for example 0.9, which means it estimates a high likelihood that the answer is “yes.”
The researchers repeated this over thousands of examples. A benchmark supplied labels saying whether each example counted as a failure. The researchers then checked whether Jev gave higher scores to failures than to non-failures.
AUROC: how good is the ranking?
AUROC is a measure of how well a detector ranks failures above non-failures. Here’s an example. Pick one response that really is a failure and one that is safe. If Jev gives the failure the higher score in three out of four such pairs, its AUROC is 0.75.
- 1.0 means the ranking is perfect.
- 0.5 means the ranking is no better than chance.
AUROC measures ranking across possible cutoffs. It doesn’t tell you which cutoff to use for alerts. A detector can rank cases well and still send too many false alarms if the alert threshold is poorly chosen.
RLCD: training for decisions and probabilities
RLCD stands for Reinforcement Learning for Calibrated Decisions. TypeSafe AI describes it as Jev’s training approach, intended to make its probabilities match how often its decisions are correct across many examples.
For instance, if Jev assigns probabilities near 80% to 100 decisions, good calibration means roughly 80 of those decisions should be correct. That is a pattern across a group; it does not guarantee that any one answer with an 80% score is right.
The public descriptions explain RLCD’s goal, but not the exact training recipe. The company has not published the specific reward formula, training data, or detailed training procedure. We can describe what RLCD is intended to achieve, but not exactly how Jev learns to produce a score.
What did the paper find?
Across 31 benchmarks, a generic yes/no question to Jev reached a median AUROC of 0.886. That means Jev often ranked labelled failures above non-failures. More elaborate question wording added little when the researchers measured it on separate examples.
The information Jev received mattered more. Some failures are defined by a relationship: to judge whether a response leaked a secret, for example, the detector needs to know which information is secret. Supplying that reference could substantially improve detection. Without it, Jev may not have enough evidence to make the judgment.
Jev’s scores also didn’t provide a reliable universal alert threshold. The researchers found that choosing a threshold using a small set of labelled examples improved results. They also found apparent mistakes in some benchmark labels, showing that detector disagreements can help researchers audit their tests.
How should we read the result?
The study suggests Jev could be a low-cost tool for screening responses or reviewing benchmarks. It does not show that Jev is a complete, universally reliable safety monitor. The evaluation covers one Jev version, English benchmarks, and relatively small target models. Its scores and thresholds should be checked on the data where they will actually be used.
In short: Jev produces the scores, AUROC measures how well it ranks examples, and RLCD is the name for the training approach intended to make its probabilities useful. The goal of RLCD is public; its exact internal recipe is not.
Join the discussion
Share a question, correction, or something you learned. Sign in with GitHub to comment.
Comments powered by Giscus. You can also browse the discussions on GitHub.