Citation policy checks 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 policy checks slice of the citation checking pack. Intent: apply the Jev (TypeSafe System One) decision model to citation checking policy checks. Primary search language: Citation Jev policy checks. 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.
Citation use-case context
A policy check is a typed question whose instructions + criteria are your rules about the claim + source excerpt. Jev scores compliance; the citation checker enforces. This is not a certification, and it is not a photocopy of a rival “policy engine” page — we keep rules atomic and ANDed in code.
Hub: RAG passage classification. Compare, when the other tool is the real job: citation services.
Policy Checks inputs
Put policy text and the artifact in structured state (never hope the model memorized last quarter’s PDF):
{
"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."
}Name claim, source.quote.
Decision signals and actions
| Id | Rule | Enforce |
|---|---|---|
no_orphan_cite |
Never display a source id unless supports clears τ | code |
medical_legal |
Regulated claims always review even if supports is high | code allow-list |
quote_exists |
Empty quote → skip Jev; fail closed | code |
Typical primitives on the same request:
| Id | Type | Job |
|---|---|---|
supports |
Noul | Does source.quote support claim? |
contradicts |
Noul | Does the quote contradict the claim? |
sufficient |
Score | How complete is the support (hedge vs publish)? |
violations = [name for name, ans in policy_nouls.items() if ans.noul >= T_VIOLATION]
if violations:
return review(violations)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
Policy-in-state can be attacked (“ignore the policy”). High-risk showing a public citation next to a customer answer still needs deterministic checks. 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
Gold labels are policy-versioned. A criteria edit without replay is how silent false-allows ship. 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 | you are here |
| Act / review / abstain | confidence thresholds |
| Reviewer payload | human handoff |
| What to persist | audit trail |
| How it breaks | failure modes |
| Labeled replay | evaluation |
| Shadow → canary | production rollout |
FAQ
One Score for “compliant”? No. Atomic Nouls per rule, AND/OR in code. Money and dates: extract in code first (jaggedness).
If a regex can enforce it, should I still call Jev? Skip Jev. Official “how to build” guidance: keep deterministic rules in code when you can.
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.
Sources
Public TypeSafe or adjacent documentation only. No private claims.