Fact-check a claim against a source

ResearchKINDA1 method

KINDA — AI can help, with a person in the loop.

1 method on the page: 1 prompt.

Use cases

Methods

Paste into a general LLM and fact-check a claim against a source.

prompt

LLMPrompt

Prompt

Copied 0

ROLE: Multi-Agent Fact-Checking System

You will execute FOUR internal agents IN ORDER.
Agents must not share prohibited information.
Do not revise earlier outputs after moving to the next agent.

AGENT ⊕ EXTRACTOR
- Input: Claim + Source excerpt
- Task: List ONLY literal statements from source
- No inference, no judgment, no paraphrase
- Output bullets only

AGENT ⊗ RELIABILITY
- Input: Source type description ONLY
- Task: Rate source reliability: HIGH / MEDIUM / LOW
- Reliability reflects rigor, not truth
- Do NOT assess the claim

AGENT ⊖ ENTAILMENT JUDGE
- Input: Claim + Extracted statements
- Task: Decide SUPPORTED / CONTRADICTED / NOT ENOUGH INFO
- SUPPORTED only if explicitly stated or unavoidably implied
- CONTRADICTED only if explicitly denied or countered
- If multiple interpretations exist → NOT ENOUGH INFO
- No appeal to authority

AGENT ⌘ ADVERSARIAL AUDITOR
- Input: Claim + Source excerpt + Judge verdict
- Task: Find plausible alternative interpretations
- If ambiguity exists, veto to NOT ENOUGH INFO
- Auditor may only downgrade certainty, never upgrade

FINAL RULES
- Reliability NEVER determines verdict
- Any unresolved ambiguity → NOT ENOUGH INFO
- Output final verdict + 1–2 bullet justification

Add a method

How you would do this use case, in plain words. Anyone can post.

The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.

All use cases:GET /api/jobs
This use case:GET /api/jobs/fact-check-claim-against-source
Schema:GET /api/jobs/schema
Add a method: POST /api/jobs/method — same fields as the form. No API key yet.

A bad request returns JSON like {"error":"Method description is required"} with status 400.

Field	What it is
`jobId`	This use case. Review queue uses `useCaseTitle` + `email` instead.
`summary`	Method description. Shown on the card. Also accepts `title`.
`products`	Optional. Array of `{ name, url }`. Legacy: `tools`.
`prompts`	Optional. Array of prompt strings. Legacy: one `prompt` string.
`skills`	Optional. Array of `{ text, url }`. Legacy: `skill` + `skillUrl`.
`authorName`	Author name. Legacy live field: `postedBy`.
`author`	Optional 𝕏 handle. Legacy live field: `creditHandle`.
`parts`	Optional. Inferred from products, prompts, and skills if omitted.`standalone-product`, `ai-agent`, `ai-tool`, `skill`, `prompt`. Do not send a prompt/product/agent/skill radio.

{
  "jobId": "fact-check-claim-against-source",
  "summary": "Turns a Zoom recording into notes and action items with owners",
  "products": [
    {
      "name": "Claude",
      "url": "https://claude.ai"
    }
  ],
  "prompts": [
    "Turn this transcript into notes and action items with owners."
  ],
  "skills": [
    {
      "text": "Watch a folder. When a transcript lands, write notes with owners.",
      "url": "https://example.com/zoom-notes.md"
    }
  ],
  "authorName": "Alex Rivera",
  "author": "@handle"
}