Comparisons· Last updated 2026-09-21

Jev versus RAG pipelines

A RAG pipeline retrieves, then generates. Jev (TypeSafe System One) does not generate. It is a decision layer you can bolt onto retrieval: keep, drop, flag, or rerank passages — then a different model writes prose.

This unofficial comparison is for people who searched “Jev RAG.” Official cookbooks: classifying passages, rerank, citation check. Confirm methods and any published lifts there — we will not restated unofficial percentages as ours. Not affiliated; no keys sold.

Where Jev sits in the pipe

query → retrieve (BM25 / dense) → Jev per passage or pair → code filter
      → (optional) LLM generate → Jev citation check → code allow/block

TypeSafe’s rerank cookbook (vendor-measured): BM25 shortlists then one question per query–candidate pair; they publish top-1 / top-10 lifts on CLERC — read the cookbook for the numbers.

Failure modes (honest)

1. Huge unfiltered state — official jaggedness: accuracy falls; also the prescribed reason to classify passages first.
2. Asking Jev to summarize the pile — generation failure mode. Extract candidates in code or with an LLM, then Choice.
3. Treating schema-safe “supports” as truth — citation check can still be wrong; use confidence to review.
4. One 218-way Choice without a “none” — line-by-line search cookbook pairs a big Choice with a Noul “does the document contain an answer?”
5. Adversarial passage — injected instructions can steer jev-1.13. Test before you drop a “filter” in production.

Cite vs generate

If the product promise is “answers only from sources,” Jev can screen claims. It cannot author the sentence. Keep that boundary in the UX: show sources your code kept, not a Jev-written paragraph.

FAQ

Is Jev a vector database? No. Retrieval stays yours.

Can I skip the LLM entirely? If the user only needs a routed document id or a yes/no, yes. If they need a paragraph, no.

Hub: Comparisons. Siblings: retrieval-only, passage classification. Official: docs.typesafe.ai.