Chat without generating any free text

01 · Role in the system

What Jev does here

Jev answers typed questions with at most 255 options, so it cannot pick from 30,000 words directly. The word tree splits the vocabulary by meaning - each word glossed in one line by a cheap model, embedded, then recursively clustered - into 254 top groups. For each word of the reply, Jev picks a group (shown as its most common words), keeps the top three, then picks the best word inside each; the reply ends when "the reply is complete" outranks every word. Two deterministic anti-loop rules stop greedy repetition. The verdict is honest: short replies work (the author reports about $0.003 and 2.6 seconds each), longer ones fall apart into word salad - one calibrated decision at a time is what Jev is built for, not a chain of dependent ones.

Reconstructing language from clustered choices

Jev answers typed questions with at most 255 options, so it cannot pick from 30,000 words directly — and this experiment builds the bridge anyway. Offline, a cheap model glosses every word in one line, embeddings are computed, and the vocabulary is recursively clustered into 254 meaning-based groups. At reply time, each word of the answer is a group choice, then a word choice inside the top three groups, with the reply ending when a completion option outranks every word.

Deterministic anti-loop rules stop greedy repetition, and the README publishes the mechanism's honest verdict: short replies work at about three cents and 2.6 seconds each, while longer ones fall apart into word salad.

A negative result worth keeping

The finding the record exists to carry: one calibrated decision at a time is what Jev is built for, not chains of dependent ones. Each word choice is well-posed; the composition of many dependent choices is where the approach collapses, and the author reports that boundary instead of hiding it.

Routed through OpenRouter with author-reported cost figures, the record earns its place as the cluster's boundary marker — the experiment that maps where typed choice ends and generation must begin. Read alongside the five-word record, it draws the line between closed vocabularies that work and open ones that cannot.

02 · Control boundary

Where Jev sits

The vocabulary is clustered offline into choice-sized groups; at reply time each word is a group Choice then a word Choice, with deterministic anti-loop rules and a completion option.

Code owns the loop, permissions, thresholds, validation, and side effects. Jev owns only the bounded judgments described above.

03 · Known limits

What this evidence does not prove

• The author's own finding: replies beyond a few words fall apart into word salad, because Jev is built for one calibrated decision at a time, not chains of dependent ones.
• Calls go through OpenRouter (model typesafe/jev-1.13) rather than the native TypeSafe endpoint.
• Per-reply cost and latency figures are author-reported.

04 · Attribution

Public sources

This is a Community record: the project was published by a third-party community author.

• finetuningsingh ↗Community · github · public · checked 2026-09-20
• finetuningsingh ↗Community · demo · public · checked 2026-09-20