<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>SourceScore Blog</title>
    <link>https://sourcescore.org/blog/</link>
    <atom:link href="https://sourcescore.org/feed.xml" rel="self" type="application/rss+xml"/>
    <description>Posts on AI-citation quality, LLM grounding, and the SourceScore methodology.</description>
    <language>en-US</language>
    <lastBuildDate>Tue, 02 Jun 2026 16:31:53 GMT</lastBuildDate>
    <generator>scripts/generate-rss.mjs</generator>
    <item>
      <title>How to find reliable sources for a research paper (without guessing)</title>
      <link>https://sourcescore.org/blog/how-to-find-reliable-sources/</link>
      <guid isPermaLink="true">https://sourcescore.org/blog/how-to-find-reliable-sources/</guid>
      <pubDate>Mon, 01 Jun 2026 00:00:00 GMT</pubDate>
      <description>Start from source types that are reliable by construction — primary, peer-reviewed, official — search inside them, then verify each candidate on three signals before you cite. A faster way to find credible sources than trusting search rankings.</description>
      <category>find-reliable-sources, credible-sources, research-paper, academic, citation, guide</category>
    </item>
    <item>
      <title>Can you cite ChatGPT or AI as a source? (and how to do it right)</title>
      <link>https://sourcescore.org/blog/can-you-cite-chatgpt-ai-as-a-source/</link>
      <guid isPermaLink="true">https://sourcescore.org/blog/can-you-cite-chatgpt-ai-as-a-source/</guid>
      <pubDate>Sun, 31 May 2026 00:00:00 GMT</pubDate>
      <description>Short answer: cite the source, not the AI. You can disclose ChatGPT as a tool you used, but never as the source of a fact — it fabricates. How to reference and verify AI properly, with APA/MLA notes.</description>
      <category>cite-chatgpt, citing-ai, academic, apa, mla, ai-hallucination, guide</category>
    </item>
    <item>
      <title>How to tell if a source is reliable: a 3-signal checklist</title>
      <link>https://sourcescore.org/blog/how-to-tell-if-a-source-is-reliable/</link>
      <guid isPermaLink="true">https://sourcescore.org/blog/how-to-tell-if-a-source-is-reliable/</guid>
      <pubDate>Sun, 31 May 2026 00:00:00 GMT</pubDate>
      <description>A practical way to judge any source — does credible work cite it, does it stay current and correct itself, and are people citing it now — plus how to check 130+ sources instantly on the SourceScore Index.</description>
      <category>source-reliability, credibility, evaluating-sources, citation, guide, fact-checking</category>
    </item>
    <item>
      <title>Multi-LLM grounding in 2026 — build once, deploy across OpenAI, Anthropic, Google, and open-weight</title>
      <link>https://sourcescore.org/blog/multi-llm-grounding-2026/</link>
      <guid isPermaLink="true">https://sourcescore.org/blog/multi-llm-grounding-2026/</guid>
      <pubDate>Sun, 17 May 2026 00:00:00 GMT</pubDate>
      <description>Single-provider lock-in is fragile in 2026. Pricing shifts, capability changes, and outages all argue for portability. The architecture pattern that keeps your grounding layer LLM-agnostic — same verification, citation, and source-quality across every provider.</description>
      <category>multi-llm, architecture, portability, router, adapter, grounding</category>
    </item>
    <item>
      <title>Six grounding strategies that actually reduce LLM hallucination (and the trade-offs)</title>
      <link>https://sourcescore.org/blog/llm-grounding-strategies-2026/</link>
      <guid isPermaLink="true">https://sourcescore.org/blog/llm-grounding-strategies-2026/</guid>
      <pubDate>Sun, 17 May 2026 00:00:00 GMT</pubDate>
      <description>Prompt engineering buys 10-30%. Retrieval-augmented generation buys another 20-40%. Signed-claim verification closes the long tail. Six strategies, their measured impact, and when to combine.</description>
      <category>grounding, hallucination, rag, verification, production, patterns</category>
    </item>
    <item>
      <title>LLM framework comparison 2026 — LangChain vs LlamaIndex vs OpenAI tools vs DSPy vs Pydantic AI vs Vercel AI SDK vs Anthropic SDK</title>
      <link>https://sourcescore.org/blog/llm-framework-comparison-2026/</link>
      <guid isPermaLink="true">https://sourcescore.org/blog/llm-framework-comparison-2026/</guid>
      <pubDate>Sat, 16 May 2026 00:00:00 GMT</pubDate>
      <description>Seven LLM frameworks own most of 2026 dev mindshare. They optimize for different things — orchestration, retrieval, type-safety, vendor-native, deployment ergonomics. Pick by archetype + audience + commitment.</description>
      <category>framework, comparison, langchain, llamaindex, openai, anthropic, dspy, pydantic-ai, vercel-ai-sdk</category>
    </item>
    <item>
      <title>Why VERITAS doesn&apos;t ship performance-comparison claims (and what we ship instead)</title>
      <link>https://sourcescore.org/blog/why-no-performance-claims/</link>
      <guid isPermaLink="true">https://sourcescore.org/blog/why-no-performance-claims/</guid>
      <pubDate>Sat, 16 May 2026 00:00:00 GMT</pubDate>
      <description>Benchmark numbers vary by prompt format, model version, shot count, and evaluation harness. Shipping them as &apos;verified claims&apos; is the surest way to make the catalog wrong by Thursday. Here&apos;s the alternative.</description>
      <category>methodology, trust, benchmarks, veritas</category>
    </item>
    <item>
      <title>Verifying AI-generated facts in 5 lines of Python</title>
      <link>https://sourcescore.org/blog/verify-ai-facts-five-lines-python/</link>
      <guid isPermaLink="true">https://sourcescore.org/blog/verify-ai-facts-five-lines-python/</guid>
      <pubDate>Sat, 16 May 2026 00:00:00 GMT</pubDate>
      <description>Drop SourceScore VERITAS into your LLM pipeline as a post-generation check. Every claim the model emits gets a confidence score + canonical citation before the user sees it.</description>
      <category>tutorial, python, veritas, hallucination</category>
    </item>
    <item>
      <title>Stop hallucinating: a developer API for grounding LLM responses with signed, sourced claims</title>
      <link>https://sourcescore.org/blog/launching-veritas/</link>
      <guid isPermaLink="true">https://sourcescore.org/blog/launching-veritas/</guid>
      <pubDate>Sat, 16 May 2026 00:00:00 GMT</pubDate>
      <description>VERITAS is a free-tier-friendly API that returns hand-verified AI/ML claims with their primary sources, an HMAC-SHA256 signature, and a ready-to-paste citation.</description>
      <category>launch, veritas, api, llm-grounding</category>
    </item>
  </channel>
</rss>
