Citation evaluation with Jev
A generator produced a claim and a source pointer. Jev answers whether the source supports the claim. Code decides publish, hedge, or strip the citation.
This unofficial page is the evaluation slice of the citation checking pack. Intent: apply the Jev (TypeSafe System One) decision model to citation checking evaluation. Primary search language: Citation Jev evaluation. Confirm patterns on docs.typesafe.ai. This site does not sell, issue, or proxy TypeSafe keys. Use a credential you already have from the console or a documented gateway.
Independent angle (cover ≠ clone): Cite vs generate boundary + failure modes. Cover the citation-check intent; do not mirror a citation-check-noul recipe slug.
Gold is supports / partial / contradicts on frozen claim–quote pairs. Do not reuse RAG relevance labels.
Citation use-case context
Evaluation for citation checking is a frozen harness, not a vibe check and not an opinion-blog “Jev review.” Labels: supports / partial / contradicts on a frozen claim–quote set. We publish no unofficial accuracy.
Hub: RAG passage classification. Compare, when the other tool is the real job: citation services.
Evaluation inputs
Replay the same contract you ship:
{
"claim": "Pro plans include a 14-day refund window.",
"source": { "id": "kb-refunds", "quote": "Pro subscribers may request a refund within 14 days of purchase." },
"answer_draft": "Yes — you have two weeks on pro."
}Freeze questions, criteria, and jev-1.13.0. Record the response model.
Decision signals and actions
Score these, not a blog-grade star rating:
- False publish rate (unsupported citation shown)
- False strip rate (good citations removed)
- Reviewer disagreement — tighten criteria, not τ theater
Pair auto-act errors with handoff rate. If the citation checker never acts, you have not evaluated citation checking — you have evaluated a human queue.
Do not treat a Noul of 0.5 as a “medium” citation checking score — it means yes and no are equally likely. Conjunctions stay in your code.
Guardrails and escalation
Promote a threshold only when the harness says auto-act error ≤ SLA and reviewers still catch the residual. TypeSafe’s confidence-gated examples use a lower bar for recoverable reads than for irreversible actions. Those numbers are illustrations. For citation checking, treat public_citation as the high bar (showing a public citation next to a customer answer). Tune on labels — see offline evaluation.
Evaluation and rollout notes
After any criteria edit, rerun before production. Cookbook lifts you see on TypeSafe pages are vendor claims — re-measure on your claim + source excerpts. Pin jev-1.13.0 (the versioned id) after you fit thresholds. jev-latest and the marketing line jev-1.13 can move. Log the response model. TypeSafe’s published list price for jev-1.13 is $0.042 per million input tokens (vendor claim — confirm on the models page); output tokens are free on that same page. Unused distractors still bill as input.
Official Python and JavaScript SDKs read TYPESAFE_API_KEY and retry documented 429/529. This site does not sell, issue, or proxy TypeSafe keys. Use a credential you already have from the console or a documented gateway.
Pack map
| Slice | Page |
|---|---|
| Graph and primitives | decision workflow |
What may enter state |
input contracts |
| What to gather first | evidence collection |
| Atomic rules | policy checks |
| Act / review / abstain | confidence thresholds |
| Reviewer payload | human handoff |
| What to persist | audit trail |
| How it breaks | failure modes |
| Labeled replay | you are here |
| Shadow → canary | production rollout |
FAQ
Will jev.pro publish a leaderboard for this use case? No. Measure on your labels. Vendor cookbook figures stay labeled as vendor claims.
What must stay frozen? Questions, criteria, and the pinned model id. Aliases can move.
Where is the rest of the Citation pack? Start with Citation failure modes and Citation production rollout. Cluster hub: Use cases.
Can Jev write the bibliography? No. It judges support. Formatting and URL fetching stay in code or another tool.
Is this the same as RAG passage relevance? Related but not the same intent. Relevance is “can this passage help?” Citation is “does this quote support this claim?”
What this page does not claim
- Not a plagiarism checker or fact API.
- No invented support accuracy.
- Not official TypeSafe.
- Official TypeSafe status, or that jev.pro issues API keys.
- That a schema-constrained answer is automatically factually correct.
Disclaimer
This is an independent unofficial site and is not affiliated with TypeSafe AI; official documentation is available at https://docs.typesafe.ai.
Primary documentation: https://docs.typesafe.ai. Hub: Use cases.
Sources
Public TypeSafe or adjacent documentation only. No private claims.