User repository on GitHub
Typed decisions from a System One model, where uncertainty is something you have to handle.
- Forks
- 1
- Last pushed
- Updated Oct 2026
Repo stats from the GitHub API, cached Oct 2026.Homepage
CommunityJev Tools & CLIs
Qualm — qddegtya
A TypeScript client for Jev where every decision must handle an unsure branch, so a low-confidence answer escalates instead of collapsing silently into a boolean.
- Stars
- 2
- Language
- TypeScript
- License
- MIT
- Published by
- Community
- Author
- qddegtya
- Last verified
- Oct 2026
This is one of several Jev listings for the same project. The canonical entry is Qualm — RoderickQiu.
About this project
Typed decisions from a System One model (TypeSafe's Jev), where uncertainty is something you have to handle. A judgment that collapses to boolean, or to a bare argmax, throws away the one signal that tells you when to escalate. qualm never does that: every decision has an unsure branch, and the compiler will not let you forget it. Jev is the model. This is what qualm adds on top of calling its HTTP API yourself.
Quoted from the project's README. Read the full README.
Works forJev for Classification
Used inJev for Software & DevTools
- Languages
- TypeScript
Highlights
- decide is a total switch: every label needs a handler, unsure needs a handler, and a missing branch is a compile error.
- Labels come back as the literal union you declared, so a typo in a branch name fails to compile rather than missing silently.
- The unsure branch is where an LLM call goes; decide passes the promise straight through without special-casing the handover.
- Zero runtime dependencies, ESM and CJS with separate declarations, and it runs in Node, Workers, Deno, Bun and the browser.
Watch out
The confidence bar is a guess and the README says so: the default is 0.7, it is arbitrary, there is no principled value, and you should measure your own data and set your own. Confidence landing exactly on the bar counts as sure. Reading the top label deliberately skips the uncertainty check, and it is named top rather than value because it is only the one that came first, so a 0.34 against 0.33 split still has a top. decide is never async itself, which means mixing a synchronous branch with an async one gives you a union, and forgetting to await turns escalation into fire-and-forget; the README recommends keeping a no-floating-promises rule enabled. The Cloudflare provider is built from the documented wire format and the README notes one detail has not been confirmed against a live response. The README is long and the digest is truncated mid-sentence in that provider section. Copy reviewed against the repository README on 2026-10-04, not from running it.
Questions about this entry
Short answers drawn from the linked project or page.
The argument is that the alternative throws away the signal you need. A judgment collapsed to a boolean or an argmax discards the one value that tells you when to escalate, so unsure is a required key a decision will not compile without, and adding a label later breaks every decide call until you handle it. The default bar is 0.7 and unsure runs whenever confidence falls below it, with confidence exactly on the bar counting as sure. Handlers take no arguments, so the escalation is an ordinary closure in scope.
Measure your own data. The README is blunt that the default is arbitrary and that there is no principled value to pick. You can set the bar per client for everything it asks, or per call for the decisions that matter more, such as a branch that deletes things. The threshold is checked against the distribution Jev returns rather than a correctness guarantee, so a high number tells you the model was sure, not that it was right.
There are two providers behind one API, TypeSafe's endpoint and Cloudflare Workers AI, with keys read from the environment at call time and importing the package running nothing, as its side-effects-free metadata promises. The honest caveat is in the README's own provider section, which says the Cloudflare wire format is built from documented shape and that one detail has not yet been confirmed against a live response. The digest we reviewed cuts off inside that sentence, so check the current README before relying on it.
You get that branch's promise back and await flattens it. If every branch is synchronous you get a plain value with no await and no microtask, which is why the same decision works inside a filter callback. Mix a synchronous branch with an async one and the return type is a union, so forgetting the await makes escalation fire-and-forget with nothing to catch it. The README's advice is to keep a type-aware linter such as no-floating-promises on.
is answers a proposition and gives a probability, choice selects among labelled options and gives top, confidence and probabilities, and score rates an ordered rubric and gives a value and legend. Each keeps its full distribution.
The onUsage callback reports the token counts and the concrete model version that answered, so metering does not mean re-parsing the response yourself.
It does jittered backoff on 429 and 5xx honouring Retry-After, has a default timeout covering the whole call, supports AbortSignal, and throws ApiError carrying the status and parsed body.
More Jev resources like this
38GitHub stars
Python memory filter that judges every stored memory against the current request with one calibrated yes/no per memory in a single Jev request, keeping everything above a threshold.
Jev Tools & CLIs#community#jevbest#catalog-import
Community
samdotmak/jev-recallTypeScript
samdotmak/jev-recallTypeScript36GitHub stars
Stock decision terminal that gathers Valyu market evidence across five categories and uses Jev for a typed 30-day outlook with probability, signals, and timing.
Jev Tools & CLIs#community#jevbest#catalog-import
Community
unicodeveloper/jevocksTypeScript
unicodeveloper/jevocksTypeScript4GitHub stars
Playful chat demo that makes Jev hold a conversation one word at a time by picking from a compact 979-word vocabulary through repeated Choice calls.
Jev Tools & CLIs#community#jevbest#catalog-import
Community
mkotlikov/jev-grugTypeScript
mkotlikov/jev-grugTypeScript4GitHub stars
Shell CLI that sends state plus noul, choice, and score questions to Jev in one request and prints probabilities, choices, and rubric positions for pipes and scripts.
Jev Tools & CLIs#community#jevbest#catalog-import
Community
y0usaf/typesafe-cliTypeScript
y0usaf/typesafe-cliTypeScript5GitHub stars
Local-first app that extracts document text on the machine and files it into configured category folders using typed Jev decisions for category, confidentiality, prompt-injection risk and subject, with a per-run audit that previews and undoes every move.
Jev Tools & CLIs#community#jevbest#catalog-import
7GitHub stars
PDF search that asks Jev one noul per line, does this line answer the query, and ranks the lines by the returned probability, so matches highlight without embeddings, a vector index or a chunking strategy. Text is extracted locally with pdf.js and the key stays on the server.
Jev Tools & CLIs#community#jevbest#catalog-import
Community
kylemclaren/jevpdfTypeScript
kylemclaren/jevpdfTypeScriptFrom the Jev guides
Original write-ups on what this entry is for.
The request shape barely changes across surfaces; the surrounding contract does. When to call the API directly and when a gateway, a Worker binding, or a router entry earns its extra hop.
Jev Tools & CLIs#gateway#vercel#cloudflare
Read article
Taking a decision checkpoint out of Python: what the GGUF and browser WebGPU exports preserve, what they change, and the parity evidence the model cards publish.
Jev Tools & CLIs#open-models#local#onnx
Read article
Jev labels a record that already exists. Code moves, flags, or holds it. How the document, mail, and transfer tools keep the action out of the model.
Jev Tools & CLIs#classification#email#security
Read article
From the Jev community
Posts from builders shipping with Jev right now.