惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

MyScale Blog
MyScale Blog
Jina AI
Jina AI
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
阮一峰的网络日志
阮一峰的网络日志
P
Proofpoint News Feed
Last Week in AI
Last Week in AI
博客园 - 司徒正美
Martin Fowler
Martin Fowler
T
Tailwind CSS Blog
B
Blog RSS Feed
Vercel News
Vercel News
博客园 - 聂微东
I
InfoQ
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
M
MIT News - Artificial intelligence
Recent Announcements
Recent Announcements
GbyAI
GbyAI
L
LangChain Blog
酷 壳 – CoolShell
酷 壳 – CoolShell
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
Microsoft Security Blog
Microsoft Security Blog
C
Check Point Blog
MongoDB | Blog
MongoDB | Blog
B
Blog

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
RAG pilots fail when the sources are not ready
Mindtrovert Labs · 2026-06-04 · via DEV Community

Mindtrovert Labs

Most RAG pilot problems are not model problems at first.

They are source problems.

The demo looks promising because the happy-path question is easy. Then the pilot meets real internal documents:

  • duplicated policies;
  • stale PDFs;
  • contradictory SOPs;
  • screenshots with important text;
  • docs with no owner;
  • files that answer "what" but not "when this changed";
  • permissions that do not match how the assistant will be used.

Before choosing embeddings, chunking strategy, rerankers, or agent tooling, I like to check whether the source layer can support a useful answer.

The quick filter:

  1. Which source is authoritative when two documents disagree?
  2. Who owns each source?
  3. How often does it change?
  4. Can the system cite the exact source passage?
  5. What questions should the assistant refuse?
  6. What questions require escalation to a human?
  7. What is the cost of a confident but unsupported answer?

That last one matters. A RAG system that says "I do not know" is often safer than one that confidently blends two outdated documents.

A small pilot should usually prove four things:

  • retrieval finds the right source;
  • the answer stays inside the source;
  • citations are inspectable;
  • unsupported questions are refused or escalated.

If those are not true, improving the prompt is usually the wrong first fix. The next milestone should be source cleanup, evaluation questions, and refusal criteria.

I packaged a small RAG evaluation kit and a fixed-scope async readiness review for teams that want to check this before funding a bigger internal assistant:

RAG Pilot Readiness Review:
https://mindtrovertlabs-sketch.github.io/scopegrade-storefront/rag-pilot-readiness-review.html

RAG Pilot Evaluation Kit:
https://mindtrovertlabs-sketch.github.io/scopegrade-storefront/

Free preview:
https://mindtrovertlabs-sketch.github.io/scopegrade-storefront/preview.html

This is a planning/evaluation resource, not a guarantee of accuracy, compliance, or production readiness. The goal is to make the first pilot milestone honest before more engineering time gets spent.