How JEV scoring works
Every launch on Fresh Weights carries a JEV traction score from 0 (obscure) to 1 (everywhere). It is not a popularity contest and it is not a black box. This page states exactly what is asked, what is fed in, and where the score can mislead.
The short version
The exact question
Word for word, this is what JEV is asked about every launch:
JEV answers typed questions against a state object and returns a structured verdict, not free text. The "noul" question type used here returns a number on a 0 to 1 scale. There is no prompt engineering around it and no second question.
What JEV sees
The state object for a launch has exactly five fields, written by our curation pipeline from primary sources:
- title
- The launch name, as announced.
- summary
- One line on what it is, in our words.
- usp
- Why it matters, in our words.
- source
- Where it was first found: GitHub, X, Hacker News, a lab account, and so on.
- github_stars
- Star count at scoring time, or 0 for non-GitHub launches.
What JEV never sees
Vendor marketing copy is not in the state. The summary and USP are rewritten from primary sources, never pasted from an announcement. There is no sponsorship input anywhere in the pipeline, so there is nothing a vendor could buy even if they wanted to. JEV also never sees our opinions: the question is fixed and identical for every launch.
How the score is used
- The traction badge.The 0 to 1 number on every card. You can sort the whole radar by it.
- The "early" badge.Launches scoring below 0.35 are flagged early: new and not yet proven, by definition.
- The Spotlight debate.Five models (GPT-6 Sol, Claude Sonnet 5.5, Xiaomi MiMo, Qwen, Kimi) argue over the week's launches once a day; JEV breaks the ties. Every finalist is also red-teamed for risk, and anything scoring 0.75 or above on risk is vetoed outright.
- Ideas get a different score.Build ideas carry a separate JEV confidence score: how likely the idea is to succeed. It penalizes ideas that depend on scraping, personal-account sessions, or automation that violates terms of service.
When it is scored
Each launch is scored once, on the day it is added, as part of the four daily update runs. Scores are not re-run later: a launch that blows up a month after listing keeps the score it earned at birth. Treat the number as a first impression from launch week, not a live meter.
Limits, stated plainly
A score is a model's judgment over curated evidence. It is not a measurement of downloads, users, or revenue, and it is comparable across launches without being calibrated to any of those. Three consequences follow:
Common questions
Can a launch game its score? It would have to game the underlying evidence: real stars, real builds, real mentions across independent sources. There is no form to fill and no one to email.
Why did a good launch score low? Usually thin evidence at scoring time. The score is a launch-week first impression; the community-builds section on each card is the better trailing indicator.
Which model does the scoring? JEV runs as typesafe/jev-1.13 via OpenRouter. Scoring is budget-capped, so it can never starve the radar's update budget.
Get the week's best AI launches, plus 3 ideas worth building
One email every Saturday. Ranked by traction, not hype. Free.