JEV - A joint does not need a brain

Jev is TypeSafe's System One model. It does not write free text. It returns a probability for each closed question, on the nodes where rules run out and a chat model would be wasted.

Folkbench folkbench.com

Co-author: folkbench.com (Folkbench is a reviewable evaluation and selection platform for AI APIs, model services, and related sites. It draws on published service information, prices, availability, latency, and evidence windows to help users compare and choose a path.)

Ten pieces in this series:

Foundation models have crossed the line. Most people can no longer pose a task that sits beyond them. The questions you can think of, current models can mostly take. Comparing who chats a little better does not hold up a new product. The difference has moved to product definition. Jev is defined for this stage.

It is TypeSafe AI's System One model. It does not generate free text. You give it a piece of state, text or program state, plus a set of closed questions. Each question comes back as a probability distribution.

It does not sell chat. It sells the joints in a system.

Nodes come in kinds. Some can be written down as rules, and then they are done. Some have to be reasoned out in the open and spoken through to a person. That is work for a brain. A batch remains in the middle. Rules cannot exhaust it. Calling a brain for it is waste. The joint sits on that batch.

A bend is enough

When you walk, the knee does not ask the brain. Hard ground, it bends a little. A steep slope, it holds. No explanation, and no draft.

A joint does not need intelligence. A joint needs instinct. Instinct sits above rules. What can be exhausted goes to rules: the state matches, take that branch; it does not match, stop. What the rules still cannot decide, but a practiced person leans toward at a glance, goes to instinct. When the reason has to be laid out, and someone has to be spoken to, call intelligence in. Do not expect one question to do the work of both rules and a brain.

Jev stays in that middle layer. The question is closed, and the shape of the answer is closed. The probability may spread. A spread means it is unsure. It only assigns probability inside the answers you gave it. The official line on a suitable question is tight: a judgment a person who knows the domain can make in a second while looking at the context. Anything that takes a long analysis does not belong as one question. Split it.

This is the same kind of work as a general classifier from before GPT. The semantic understanding is better, and it is faster. It can read a sentence that takes the long way around, and it can read an intention tucked into program state. Do not take it to chat.

The official name for the position is System One. It borrows Kahneman's System 1: fast, intuitive. The slow thinking that writes its steps out for a person to read is not in this position.

The name comes from William Stanley Jevons. After coal and steam engines became more efficient, demand did not fall. It rose. The official use of the name says that once judgment is cheap, the number of nodes in a system that need a judgment grows with it.

Only these three questions

There are only three question types.

Yes-no, called Noul. A sentence that true or false can close. What comes back is the probability of "yes", from 0 to 1. Code thresholds that number. Past the line, it runs. Short of the line, it stops, or it hands the case to a person.

Single choice, called Choice. The options are fixed in advance, at most 255. Each option can be followed by a sentence saying what it means. What comes back is the whole distribution, plus the option with the highest probability. It does not add anything that is not on the list.

Ordered levels, called Score. From 2 to 10 levels. Ranked from low to high, each level written as a concrete situation. Do not hand it only a number. The landing point may sit between two levels, and the probability of every level is still there. If the business needs an integer, code collects it.

All three can be asked in the same request. The same state, each question on its own. A yes-no does not draft the single choice. Which question to use, and which to drop, is up to the code. Adding questions barely adds time. What you add is the question's own tokens. Input is billed by token. The extra cost is that small piece.

Sampling is not the chat kind. The official account is a new architecture, parallel sampling. One pass collects every output. Not token by token. Chat models are slow because one word waits on the next, and the output gets expensive along the way. Jev does not grow one word at a time.

The training method is called RLCD, Reinforcement Learning for Calibrated Decisions. The target is calibration: the confidence it reports has to line up with how often it is actually right. "Reads like a person" is not the target.

Input is $0.042 per million tokens. Output is free. End to end is about 70ms to 500ms. Seventy milliseconds happens, and five hundred milliseconds happens. The official judgment on intelligence is stated alongside that: on System One tasks, about the same as current large models, and one to two orders of magnitude faster. That "about the same" holds only for closed judgments. Using it to write an article, or to talk an unclosed question all the way through, is not inside that claim.

Where the rules stop

Nodes of this shape are not rare. Classification, routing, scoring, review, risk control, plus the judgment nodes inside an agent, all have it. Which queue a ticket enters, which stretch of code the next hop takes, how hot a complaint is, whether one sentence is allowed through, whether an operation looks like the exception that should be stopped, whether a tool at a fork is handed over. All of these can be asked quickly, and all of them can be closed.

Rules can eat the stretch that is easy to write. Once exceptions pile up, conditions tangle. Change one, and the ones beside it may fail with it, so later nobody dares to touch them.

Some people throw the whole state at a model that can chat and ask it for a sentence of advice. A chat model can do that. The node only needs a lean. You still have to parse the sentence into a branch, and try again when that fails. Time is spent on the shape of the text.

A brain is allowed. This node does not deserve one first. Jev takes this stretch. A closed question goes in, a distribution comes out. Whether it crosses the line, and whether it escalates, is written in the code beside it. How the flow moves is still the code's business.

A refund splits into three questions: whether a refund is being asked for, whether the ask is a refund, a change of ticket, or only a question about the rules, and which level the anger lands on. Noul, Choice, and Score, looking at the same state. Sentences written into the policy stay with the rules. What the rules do not match is read from the distribution. The reply to the customer is not its job to write.

An agent splits the same way. The sentence a person finally reads is left to a model that can speak. The judgments in the middle should not wake a brain at every step. Wake it once, and that step runs at the cost of a chat. Swap the judgment for a joint, and the reply that goes out can stay as it is.

Writing needs another model

It cannot write an article. It does not generate text. Put the topic and the tone into the state, and it still only answers the closed questions you wrote. Whether something is off topic, that it can judge. The sentences have to come from another model.

Do not press an open question into a single choice. "What should we do next" has no cell in Choice until you have finished listing the ways. Split first. What can be exhausted stays with rules. What instinct can answer, write as these three questions. What needs reasoning laid out, and a person spoken to until the words are finished, that is when intelligence comes in. If it cannot be split, it is not a joint yet.

Some people hear System One as a downgrade. Rules are lower. System One is the instinct above the rules. It is fast, and it does not write an explanation. It still has to understand the meaning, or the rules would have been enough. Above that is intelligence. The official intelligence claim is "about the same" on closed tasks, and the speed claim is one to two orders of magnitude faster. With that speed, a call can sit inside a loop instead of waiting out one chat.

Once foundation models have flattened the tasks most people can pose, a product has to close into a definite interface. Jev closes into a joint. Chat is not for sale. The nodes where rules cannot be finished, and where calling a brain would be waste, are its place.

Sources

Series