Skip to content

Retrieval-Augmented Generation (RAG)

Retrieval-Augmented Generation (RAG) is an AI architecture that retrieves external documents at query time to ground a language model's responses.

Known aliases

  • naive RAG
  • RAG
  • RAG pipeline
  • retrieval
  • retrieval-only

Current stories

investConfirmed2 publishers

Bank AI job postings climb 49% to 139,819 as agent orchestration grows fastest

AI-related job postings at banks such as JPMorgan Chase, Citigroup and Capital One rose 49% this year to 139,819, according to Draup. Most of the growth is in staff who connect teams of AI agents to business lines and staff who keep those agents in check.

Perspective Coverage

3 publishers
Builder
Builder 25%
Operator
Operator 43%
Investor
Investor 32%

Reality

Evidence40
Adoption30
Hype gap+35
Incentives60
Confidence45
buildOne report1 publisher

In one RAG security guide, the adversarial ranking example clears all four sanitizer patterns

A dev.to walkthrough of RAG knowledge injection ships a four-regex document sanitizer as its first line of defense. Its own sample attack chunk matches none of the four, which leaves provenance filtering to carry the boundary.

Publishers:dev.to

Reality

Evidence57
Adoption
Not scored
Hype gap+42
Incentives28
Confidence63
buildOne report1 publisher

RAC audits each atomic fact against retrieval after the model has already answered

The paper reports up to 30% factuality gains over prior baselines with no fine-tuning, though its own introduction concedes that RAG with Google search had already cleared those baselines by more than ten points.

Publishers:arxiv.org

Reality

Evidence28
Adoption
Not scored
Hype gap+34
Incentives68
Confidence44
buildOne report1 publisher

Three hops separate the customer's question from the rule that changes the answer

Salesforce's Agentforce team argues that a correctly cited answer can still be wrong because the deciding fact lives in another system. That locates the fix in the graph schema itself; resizing chunks won't touch it.

Reality

Evidence44
Adoption
Not scored
Hype gap+12
Incentives72
Confidence58
buildOne report1 publisher

Chunking a corpus that already has block addresses just adds a redundant identity layer

The author of Doco argues that browse, search, cite and safe-edit operations over a maintained corpus do most of the work teams expect from embeddings, and that the pipeline adds a copy which drifts from the source.

Publishers:dev.to

Reality

Evidence40
Adoption
Not scored
Hype gap+12
Incentives68
Confidence52
leadershipOne report1 publisher

Revenue cycle AI buys faster cash with higher audit risk

Practitioners on the Forbes Technology Council put billing and coding at the top of both the payback list and the risk list, and most of their prescriptions land on retrieval and retention rather than on a human reviewer.

Publishers:forbes.com

Reality

Evidence22
Adoption
Not scored
Hype gap+14
Incentives74
Confidence41
buildOne report1 publisher

Move execution authority out of the model and into the tool boundary

A dev.to design note inserts code gates and a human approval between the model and the tool, which is the right shape, though a policy layer that reads a severity field the model itself wrote has not moved the authority anywhere.

Publishers:dev.to

Reality

Evidence30
Adoption
Not scored
Hype gap+22
Incentives20
Confidence45
buildOne report1 publisher

Logs behind a fluent RAG demo showed the correct chunk arriving 30% of the time

A generator writes with equal confidence whether its context is right or wrong, so the only readout that separates the layers is a labelled eval set you own, scored on the retrieval side before an answer exists.

Publishers:dev.to

Reality

Evidence42
Adoption
Not scored
Hype gap+18
Incentives32
Confidence55
leadershipOne report1 publisher

Uber's security experts withheld the Slack channels until Genie's retrieval improved

A configurable framework let Uber stand up an LLM Slack bot overnight, but a hand-written set of more than 100 questions from its own subject-matter experts decided whether that bot went near the security channels.

Publishers:uber.com

Reality

Evidence46
Adoption34
Hype gap+28
Incentives68
Confidence52
productOne report1 publisher

Ng's four AI skills came from 10,000 job reqs. The fight is over the fifth

The list reads like an engineering syllabus because it was built from engineering postings. What the critics add is the part that only surfaces after launch.

Publishers:zdnet.com

Reality

Evidence38
Adoption
Not scored
Hype gap+22
Incentives62
Confidence44
productOne report1 publisher

Alert correlation is not diagnosis, and your postmortems are the ceiling on the difference

A devops.com piece sets three tests for AI incident tools: causal reasoning, current dependency data, and a willingness to say it is not sure. The training corpus is your own postmortems.

Publishers:devops.com

Reality

Evidence26
Adoption
Not scored
Hype gap+12
Incentives32
Confidence38
buildOne report1 publisher

RAG prototypes work because a human picked the files. The drive does not come pre-curated

A builder of voice intake systems argues the model is the least interesting part of a knowledge base, and that the first deliverable is a list saying which document governs each topic.

Publishers:dev.to

Reality

Evidence27
Adoption18
Hype gap−9
Incentives62
Confidence41
buildOne report1 publisher

Persisted citations make conversation history a second read path into the corpus

A copilot that stores the source cards behind each answer has quietly built a read path its search guards never see. One developer's fix re-checks entitlements in the service at replay time.

Publishers:dev.to

Reality

Evidence45
Adoption12
Hype gap+8
Incentives25
Confidence52
buildOne report1 publisher

Anthropic's /eli5 skill: two lines of instruction, one HTML file, no room for precision

A Claude Code skill that Anthropic staff reportedly use internally emits a single standalone HTML explainer built from big pictures and few words. The constraint is the product, and also the ceiling.

Publishers:dev.to

Reality

Evidence56
Adoption24
Hype gap+24
Incentives44
Confidence48
buildOne report1 publisher

Debug the index before you swap the model: the RAG checklist works, the 73% does not

A dev.to postmortem argues most RAG failures happen in retrieval. The debugging order it recommends survives scrutiny. The headline percentage it leans on does not.

Publishers:dev.to

Reality

Evidence26
Adoption
Not scored
Hype gap+38
Incentives30
Confidence48
buildOne report1 publisher

A million 'AI slop' reports in two weeks, and not one of them measures accuracy

LinkedIn's new report button collects human quality judgements at scale. Detectors and watermarks answer only who wrote a page, which leaves retrieval pipelines to score corroboration themselves.

Publishers:dev.to

Reality

Evidence42
Adoption55
Hype gap+8
Incentives58
Confidence44
buildOne report1 publisher

Six weeks of agent-run ops: the failures were plumbing, not the model

A developer's LangGraph experiment broke on stale state and a prompt that told one agent to please another. Both fixes are engineering controls, and both cost something.

Publishers:dev.to

Reality

Evidence26
Adoption9
Hype gap+22
Incentives34
Confidence41
buildOne report1 publisher

The chunker sets the ceiling: how a character boundary turns a correct policy into a wrong answer

A worked example from a dev.to post shows a fixed-size split severing "unless defective" from a refund rule. Retrieval still ranks the mutilated chunk first, and no component reports a fault.

Publishers:dev.to

Reality

Evidence32
Adoption
Not scored
Hype gap+18
Incentives
Not scored
Confidence44
buildOne report1 publisher

The fine-tune that kept promising refunds: freshness is the bug no eval catches

A consultant baked a shipping policy into a 7B model's weights in January. The policy changed in March. The first thing to notice was a customer holding a refund window that no longer existed.

Publishers:dev.to

Reality

Evidence26
Adoption
Not scored
Hype gap+18
Incentives62
Confidence44
buildOne report1 publisher

Open Knowledge Format: when the fact already has a name, the chunker is the bug

Google Cloud's OKF, published 12 June 2026, stores concepts as markdown files addressed by path. The claim worth testing: chunking a definition you already agreed on throws away its dependencies.

Publishers:dev.to

Reality

Evidence32
Adoption18
Hype gap+34
Incentives58
Confidence40

Earlier coverage