Use cases· Last updated 2026-09-21

Citation confidence thresholds 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 confidence thresholds slice of the citation checking pack. Intent: apply the Jev (TypeSafe System One) decision model to citation checking confidence thresholds. Primary search language: Citation Jev confidence thresholds. 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.

Public citations need a higher bar than internal footnotes. Relevance-to-answerer floors from the RAG pack are the wrong τ.

Citation use-case context

Thresholds turn citation checking answers into act / review / abstain. They are product policy, not a hyperparameter TypeSafe ships. Official 0.5 / 0.9 sketches are illustrations. This slice also carries the false-reject discussion: over-gating citation checking hides calibration.

Hub: RAG passage classification. Compare, when the other tool is the real job: citation services.

Confidence Thresholds inputs

You need (1) pinned answers on a frozen contract and (2) labels for supports / partial / contradicts on a frozen claim–quote set. State shape:

{
  "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."
}

Decision signals and actions

FLOORS = {
    "internal_footnote": 0.60,      # illustrations — replace
    "public_citation": 0.90,
}
NOUL_TAU = 0.80  # for supports

def allow(ans, action):
    return ans.confidence >= FLOORS[action]

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

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.

Band around 0.5 on supports always reviews. Do not copy 0.80 onto Choice confidence.

Evaluation and rollout notes

• False publish rate (unsupported citation shown)
• False strip rate (good citations removed)
• Reviewer disagreement — tighten criteria, not τ theater

Fit loop: pin jev-1.13.0 → replay → plot error vs confidence → pick floors where auto-act error ≤ your SLA. 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

FAQ

Should public_citation use 0.9 everywhere? No. Over-gating hides calibration and dumps the queue on humans. Fit per action.

Can I reuse a Noul τ as Choice confidence? No. Jaggedness: they are not interchangeable. See confidence.

Where is the rest of the Citation pack? Start with Citation decision workflow and Citation human handoff. 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.