WeSearch

Jev Can't Be Calibrated

·3 min read · 0 reactions · 0 comments · 2 views
More from Alexmolas programming Compare coverage Trending Talk Blindspots Daily Sources Live wire
TL;DR · WeSearch summary

Jev can't be calibrated September 23, 2026 · 3 mins · 617 words Share on: X · HN Unless you’ve been living under a rock, you’ve probably heard about Jev. Simon Willison’s post is a good overview, and this one shows how to implement it in a few lines of Python. In short, Jev is TypeSafe’s first “System One Model”: instead of generating text, it takes unstructured input and returns typed decisions from a set of outputs you define in advance, each with a probability attached.

Key facts
About this source

Hacker News (Front Page) files mainly under programming. We currently carry 2,051 of its stories. Top-voted stories on Hacker News.

Original article
Alexmolas
Read full at Alexmolas →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherAlexmolas
Canonical URLhttps://www.alexmolas.com/2026/09/23/jev-cant-be-calibrated.html
Publication timeWed, 23 Sep 2026 14:39:57 +0000
Retrieval time2026-09-23T16:09:30.701Z
Last seen2026-09-23T16:09:30.701Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Clusterqw0XiQW-ckHG · 1 stories
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

Jev can't be calibrated September 23, 2026 · 3 mins · 617 words Share on: X · HN Unless you’ve been living under a rock, you’ve probably heard about Jev. Simon Willison’s post is a good overview, and this one shows how to implement it in a few lines of Python. In short, Jev is TypeSafe’s first “System One Model”: instead of generating text, it takes unstructured input and returns typed decisions from a set of outputs you define in advance, each with a probability attached. One of its selling points is that “all answers are accompanied with calibrated probabilities and confidence scores”. In this post I argue that Jev is useful, but that the calibration claim can’t hold in general, and that you should treat its outputs as scores rather than probabilities.

Excerpt limited to ~120 words for fair-use compliance. The full article is at Alexmolas.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from Alexmolas