Retrieval ✦ 88outlineNot a production recipe

Citation / claim support check

Who: RAG / research product teams. Steps: (1) Gather claim + evidence snippets (search optional). (2) Choice: supported / contradicted / mixed / insufficient. (3) Insufficient → do not assert. Expected effect: fewer hallucinated citations in generated answers.

1

Treat this as an outline — adapt state and questions to your data.

2

Implement in code — call System One / Jev; compose answers yourself.

3

Gate on confidence — act, confirm, or escalate before side effects.

Outline sketch

Prompt
Audience: RAG / research products.
Steps:
1) Claim + evidence snippets as state (search optional).
2) Choice: supported | contradicted | mixed | insufficient_evidence.
3) If insufficient → refuse to assert; else continue generation with caveats.
Expected effect: fewer unsupported citations.

Needs access to: typesafe-sdksearch-api

Who it's for

RAG / research product teams

Steps / how it's set up

Sources: citation_check cookbook · SerpApi · Getting started with Jev fact checker.

When confidence is low, route to human review instead of auto-publishing citations.

Sources (wave-2 deepen)

Expected effect

Forces an abstain path when evidence does not back the claim.

Unofficial outline for learning. Paraphrased from public docs and tutorials — not a production recipe. Review sources before you automate anything.