REPOSITORY ANALYSIS

jevrag

Replaces hardcoded RAG thresholds with explicit calibrated decision points. Five primitives (retrieval stopping, chunk splitting, context selection, answer abstention, cache trust) behind one swappable state → Decision → confidence → action interface, each evaluated on real datasets with a calibration harness that reports honestly.

E2 · source reviewedPublic material or source evidence was reviewed. A fixed-version source review requires checking a pinned revision; this is not a reproduction, performance endorsement, or safety guarantee.
Stars
3
Forks
0
License
MIT
Last commit
2026-09-22

What Jev does here

jevrag/decision.py — the `ask(state, questions) -> DecisionResult` method calls `api.typesafe.ai/v1/systemone` via the Jev backend. All five primitives in `jevrag/primitives/` route through this method.

Adds structured choices or scores to the workflow; performance and cost benefits have not been independently verified.

The cited decision and RAG-adapter files were read for stub provenance and bypassed relevance values. This site did not rerun a dataset evaluation or paid call. Stub results and None-valued bypasses must remain separate from real Jev results when computing metrics.

What task does this project fit?

Evaluate where learned judgments improve a RAG pipeline instead of replacing every threshold by default.

Material analysed:

From input to action

  1. Wrap retrieval stopping, splitting, selection, abstention or cache trust behind one Decision interface.
  2. Record decisions with backend, model and usage provenance.
  3. Compare correctness, calibration and risk-coverage on an evaluation set.

Implementation details that matter

A stub is deliberately labeled, not a cheap Jev result

decision.py's StubDecision returns fixed values with backend='stub', model='stub' and zero tokens. It exercises measurement plumbing without establishing model quality.

Inspect the supporting source ↗

Bypass can mean no measurable confidence

rag_jev_selector.py keeps bypassed relevance as None instead of inventing a score. Coverage and accuracy must preserve these omissions in their denominators.

Inspect the supporting source ↗

When to choose it

Useful when you can compare one specific RAG decision against a deterministic baseline. Keep unsupported or low-coverage primitives experimental until held-out evaluation justifies them.

How to inspect it yourself

Read DecisionResult metadata and the rag-jev adapter's selection reasons. Recompute metrics with stub/bypassed records separated from actual Jev responses.

Limits of this review

  • No dataset evaluation or paid call was reproduced here.
  • Published benchmark results and confidence thresholds are conditional on the author's datasets and policy.
Primary material used in this analysis