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)

jev
Searching Database…

What is this?A curated list of public projects, integrations, and discussions built on Jev — TypeSafe AI's System One model for typed decisions. It tracks who is actually building with it and which decision patterns transfer across industries.
What is Jev, exactly?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. Projects use it as a drop-in decision layer for classification, routing, scoring, verification, and agent guardrails.
If a project is listed, does that mean it's any good?No. Inclusion only means the rules were met — the list does not review code quality, security, maturity, or whether a project even runs. Run the README's adoption checklist before trusting an entry.
Who is this list for?Developers and teams deciding where Jev could slot into their own stack — checking which decision patterns already transfer across industries.
What does a production Jev deployment look like?Notra, a marketing analytics GEO platform, moved brand-visibility classifiers from an LLM onto Jev Boolean decisions at a 0.5 threshold, targeting 300 ms p50. In a benchmark pilot, DocJev classified 40/40 documents at about 182 ms decision p50.
Why is there a category just for discussions?Related Practices / Discussions (72 entries) captures credible public signals — X threads, Reddit discussions, and interviews — describing real Jev usage when no strong standalone case page exists yet.
What do these projects ask Jev to decide?Typed choices mostly: routers pick the cheapest capable model, an email workflow picks invoice vs general, Jev Wrapped classifies posts into ten kinds with ad and clickbait checks, and Home Assistant answers house questions as a probability, choice, or score.
Creator
yibie
Size
1.6 MB
Stars
2.4K
Updated
CommitOct 18
Age
1mo
Commits · 90 Days