JEV PROJECTS

Within a week of release the Jev project ecosystem went from nothing to a few hundred entries, and it did so in a very particular shape. Almost nobody built a Jev product. What people built were layers: a Jev project that wraps the API for one language, a Jev project that exposes Jev judgements as MCP tools, a Jev project that drops a Jev call into an agent loop that already existed.

That is what you would expect from a model that cannot do anything on its own. A Jev project is almost always a piece of plumbing between Jev and something else — a browser agent, a coding harness, a RAG pipeline, a trading strategy, a game loop. The interesting question about any Jev project is not what it is, but where in someone else's system it decided to put a decision.

WHAT THE JEV PROJECT CLUSTERS TELL YOU

The largest cluster by a distance is infrastructure: SDK wrappers, gateway adapters, MCP servers, evaluation scaffolds. That is the signature of a model people want to try in an existing system rather than build a new system around. If you are starting, this is where to look first — someone has probably already written the adapter for your stack.

Agent decisions is the second cluster, and it is the one that best explains why Jev got adopted so fast. A browser agent that calls a frontier model for every click is slow and expensive; a Jev project that swaps that per-step decision onto Jev and calls the big model only when text must be typed gets an order of magnitude on both. The same substitution shows up in coding agents, desktop automation and robotics.

Then verification and guardrails, which is where the calibration actually earns its keep. A Jev project in this group is usually a gate: judge whether a tool call is destructive, whether a completion claim is honest, whether a retrieved passage supports the claim, whether a generated answer cites what it says it cites. These are Nouls with thresholds, and they are the lowest-risk way to put Jev into something that already works.

The long tail — finance, games, moderation, data labelling, compliance — is thinner but more interesting, because each entry is someone discovering that their domain happens to be full of bounded decisions nobody had automated because the per-decision cost never made sense before.

PICKING A JEV PROJECT TO START FROM

If you want to call Jev directly, start with an official SDK and skip the wrappers. The Python package is typesafe-sdk and the JavaScript one is @typesafe-ai/sdk; both are thin, and most of the wrapper Jev projects in this index exist to bridge them into a specific framework rather than to improve on them.

If you already run an agent, look for the MCP servers. Several Jev projects expose Choice, Score and Noul as tools that Claude Code, Codex and similar harnesses can call directly, which means you can put a Jev decision in front of a risky action without writing any integration code at all.

If you want to see the shape before committing, read a small one end to end. The guardrail and context-pruning Jev projects tend to be a few hundred lines, because the interesting part is the question design rather than the plumbing. That is the fastest way to understand what a good Jev question actually looks like.

And if you are evaluating whether Jev fits at all, the decision patterns page is a better starting point than any individual Jev project — it carries the state, the questions and the routing policy for eleven recurring shapes, without the noise of someone else's codebase around it.

WHERE THIS JEV PROJECT DATA COMES FROM

Every Jev project in this index is drawn from the community awesome-jev list, which is MIT licensed and maintained by people who are not us. We parse their category files, deduplicate by URL, classify each entry as code or write-up, infer the decision type where the summary allows it, and link straight back to the original source.

We add no descriptions of our own. The one-line summary on each Jev project row is the upstream maintainer's, because rewriting someone else's summary to make it sound like ours would be both dishonest and worse.