awesome-jev README

The project's README from github.com/yibie/awesome-jev. As one markdown file: README.md.

awesome-jev

A curated awesome list of public projects and practices built on Jev, TypeSafe AI's System One model for typed decisions.

This README is the homepage aggregate of the current category files, so the latest accepted entries are visible here without drilling into subpages.

Jev is not a chat model. It takes unstructured state plus a typed question and returns a typed decision — a choice, a score, or a boolean, each with a confidence. That makes it a drop-in decision layer for software: classification, routing, rubric scoring, verification, and agent guardrails. This list tracks who is actually building with it, and which patterns transfer across industries.

The repository treats all categories equally — each entry lives in exactly one category, chosen by its direct Jev application domain. A dedicated Related Practices / Discussions category captures credible public practice signals — X threads, Reddit discussions, and interviews — that describe real Jev usage even when no strong standalone case page exists yet.

[!WARNING] A listing is not an endorsement. This project applies inclusion rules only — public, citable, genuinely uses Jev for a typed decision, one-sentence summary. It does not review code quality, security, maturity, or whether a project runs at all.

Treat same-day bulk submissions with particular care. Several repositories published together by one author, sharing a scaffold and a thin commit history, can satisfy every inclusion rule and still be unproven. Volume is not evidence of quality. See Curation is not endorsement for a checklist to run before adopting anything here.

Why this list

Most Jev discussion is scattered across launch threads, model-gateway listings, and one-off prototypes. This list answers two practical questions quickly:

This is not a comprehensive database. It is a high-signal, fast-scanning field guide.

Inclusion criteria

An entry should meet all of the following:

We do not include:

Curation is not endorsement

Inclusion means one thing: the entry satisfies the inclusion rules above. It is not a quality review, a security audit, or a recommendation. We do not verify that a project compiles, that its tests pass, that its published numbers reproduce, or that its license permits your use.

This matters most for projects that arrive in bulk. When one author releases several repositories on the same day, they commonly share a single scaffold — the same AGENTS.md, CLAUDE.md, STATE.md, and CHANGELOG.md — land in one or two commits each, and may ship considerably more prose than code. Such projects can be entirely legitimate; they are simply unproven. Treat them as leads, not as validated tools.

Before adopting an entry, check it yourself:

Check Why it matters
Does the code actually call the Jev API? An entry can read well on a README alone. Look for a real request carrying typed questions, and a parsed answer coming back.
Is there a runnable check? A test, an example with expected output, or a public demo. No check means no evidence that it works.
Do the numbers have a source? Any accuracy, latency, cost, or volume figure should be traceable to the linked page. We strip claims we cannot verify, but the project page itself may still carry them.
How much of the repository is code? Some projects are mostly prompt documents. That can be legitimate — just know which one you are getting.
Is there a license? A few entries have none, which limits reuse and redistribution.

Found something wrong? Open an issue or a pull request — removal is as valid a contribution as addition. Rules for AI-assisted work, project depth, and submission rate live in CONTRIBUTING.md.

Current coverage

Open categories still being seeded

Each entry lives in exactly one category. When a project could fit multiple categories, we choose the one closest to its direct application domain.

Browse by category

Find by coding agent

Optional tags on an entry name the coding agent it targets and the kind of integration it is. Most entries carry none — they are added only when the source itself supports the classification.

Full list

Classification & Routing

Source file: categories/classification-routing.md

Adaptive & Realtime UI

Source file: categories/adaptive-realtime-ui.md

Verification & Guardrails

Source file: categories/verification-guardrails.md

Scoring & Ranking

Source file: categories/scoring-ranking.md

Agent Decisions

Source file: categories/agent-decisions.md

Data Labeling & Curation

Source file: categories/data-labeling-curation.md

Evaluation & Benchmarking

Source file: categories/evaluation-benchmarking.md

Calibration & Research

Source file: categories/calibration-research.md

Infra / SDKs / Integrations

Source file: categories/infra-sdks-integrations.md

Game & Simulation

Source file: categories/game-simulation.md

Finance & Trading

Source file: categories/finance-trading.md

Source file: categories/compliance-legal.md

Content Moderation

Source file: categories/content-moderation.md

Source file: categories/related-practices-discussions.md

Submission format

Use exactly one line per entry:

- [Name](URL) - Industry: one-sentence description of the Jev use case.

How to contribute

  1. Pick the category that best matches the direct Jev application domain.
  2. Add a single-line entry in the required format to the category file, not directly to the README aggregate.
  3. Keep the summary concrete and scannable.
  4. Prefer examples that clearly show scenario + typed decision + value.

See CONTRIBUTING.md for details.

License

MIT

awesome-jev (yibie/awesome-jev)

Searching Database…

这是做什么的?这是一个精选清单,收录基于 Jev 构建的公开项目、集成方案和讨论。Jev 是 TypeSafe AI 推出的 System One 模型,用于做出带类型的决策。这份清单记录了谁在实际使用它构建产品,以及哪些决策模式可以跨行业复用。
Jev 到底是什么?它不是聊天模型——它接收非结构化的状态和一道带类型的问题,返回一个带类型的决策结果:一个选项、一个分数或一个布尔值,每种结果都附带置信度。项目把它当作即插即用的决策层,用在分类、路由、打分、校验和智能体防护栏等场景。
项目被列进来,是不是说明它不错?不是。收录只代表符合规则——这份清单不审查代码质量、安全性、成熟度,甚至不确认项目能不能跑起来。在信任某个条目之前,请先按 README 里的采用检查清单过一遍。
这份清单是给谁看的?面向正在考虑把 Jev 引入自己技术栈的开发者和团队——帮他们了解哪些决策模式已经可以跨行业复用。
生产环境里的 Jev 部署是什么样的?营销分析 GEO 平台 Notra 把品牌可见度分类器从 LLM 迁移到了 Jev 的布尔值决策上,阈值设为 0.5,目标是 p50 延迟 300 毫秒。在一个基准试点中,DocJev 对 40 篇文档全部完成分类,决策 p50 延迟约为 182 毫秒。
为什么专门设一个“讨论”分类?Related Practices / Discussions(72 条)用来收集可信的公开信号——X 帖子、Reddit 讨论和访谈——在没有足够分量的独立案例页面时,记录 Jev 的真实使用情况。
这些项目都让 Jev 决策什么?大多是带类型的选项:路由器挑选能胜任任务的最便宜模型;一个邮件流程判断邮件是发票还是普通邮件;Jev Wrapped 把帖子分成十类,并做广告和标题党检测;Home Assistant 用概率、选项或分数来回答关于房子的问题。
Creator
yibie
Size
1.4 MB
Stars
2.4K
Updated
CommitOct 17
Age
1mo
Commits · 90 Days