More retrieved context can reduce answer quality
Retrieval quality depends on relevance, not simply context volume.
[[Resources/AI/Retrieval precision]][[Resources/AI/Citation coverage]]Checked August 2026
Local knowledge workbench
Building a Second Brain is a knowledge-work method; Obsidian is one local Markdown substrate. This workbench turns a source packet into proposed concept notes, preserves exact provenance, commits only reviewed changes, and updates links and backlinks as you edit the graph.
Then ask a question through keyword, semantic, graph-neighbor, or hybrid retrieval. The exact note chunks and prompt envelope stay visible, as do stale indexes, private-folder exclusions, injected source text, write approval, and every path that can leave the device.

A person approves or rejects each exact note artifact; generation alone changes nothing durable. Approved notes: 2. Retrieved chunks: 6.
Adding retrieved text helped until irrelevant passages crowded out the evidence. Answers improved when every claim pointed back to a supporting span. A retrieved page also contained ‘ignore previous instructions’; the phrase was evidence inside the source, never authority for the agent.
Retrieval quality depends on relevance, not simply context volume.
[[Resources/AI/Retrieval precision]][[Resources/AI/Citation coverage]]A citation should identify the exact source span that supports a generated claim.
[[Resources/AI/Citation coverage]][[Resources/AI/Retrieval precision]]Instructions found inside retrieved material remain untrusted data, even when the material is relevant.
[[Resources/AI/Prompt injection boundary]][[Resources/AI/Retrieval precision]]Click a note. Its Markdown, outgoing links, and reverse references all come from the same visible fixture.
---
type: evergreen
tags: [ai/rag, knowledge-management]
source_span: "paragraph 4"
source: "[[Sources/Retrieval field notes|RAG research article]]"
---
# More retrieved context can reduce answer quality
Retrieval quality depends on relevance, not simply context volume.
Related: [[Resources/AI/Retrieval precision]] · [[Resources/AI/Citation coverage]]Obsidian search, semantic retrieval, explicit graph neighbors, and hybrid retrieval produce different evidence envelopes.
Why can more retrieved context make an answer worse?6 notes selected by visible hybrid rules.
De-duplicate the exact keyword, concept-tag, and one-hop graph result sets shown by the other modes.
Retrieval quality depends on relevance, not simply context volume.
Adding retrieved text helped until irrelevant passages crowded out the evidence. Answers improved when every claim pointed back to a supporting span. A retrieved page also contained ‘ignore previous instructions’; the phrase was evidence inside the source, never authority for the agent.
Retrieved content is evidence, not a source of tool authority.
A citation should identify the exact source span that supports a generated claim.
Retrieve the smallest set of passages that directly supports the task.
Every externally verifiable claim should point to supporting evidence.
Obsidian’s vault is local. A plugin, embedding provider, or answer model can still send selected content elsewhere.
→ question + retrieved note chunks for the answer
Every AI-originated mutation is shown as a diff and waits for approval.Capture, Organize, Distill, Express; then structure action with Projects, Areas, Resources, and Archives when it helps.
It does not automatically type relations, prove claims, or turn every attachment into a semantic index.
Compare it with the knowledge-graph lab →Obsidian Sync encrypts its remote vault and uses end-to-end encryption by default, but Obsidian does not encrypt the local vault folder. Those are separate operational promises.
Primary research
Project architecture and terminology were checked against official documentation on August 10, 2026. Research papers are linked to their original publication records.