Local knowledge workbench

Build an AI second brain in Obsidian—without hiding the files

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 tactile local knowledge vault made from linked note cards, backlink threads, maps of content, and dark volcanic glass forms
Second Brain workbench · Durable local notes, inspectable links, reviewable AI
Manipulate
Source · approvals · wikilinks · retrieval · model boundary
Inspect
Markdown · YAML · backlinks · chunks · provenance
Safety premise
Local vault ≠ automatically local AI
Second Brain workbenchDurable files first · AI changes stay reviewable
Current knowledge stepInspect before mutation

A person approves or rejects each exact note artifact; generation alone changes nothing durable. Approved notes: 2. Retrieved chunks: 6.

01 · Original sourceRAG research articleSources/Retrieval field notes.md
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.
Provenance
paragraphs 4–6
Source state
Preserved separately
Authority
Untrusted evidence
02 · Proposed notesNothing saves silentlyApprove, reject, or inspect the exact artifact
paragraph 4

More retrieved context can reduce answer quality

Retrieval quality depends on relevance, not simply context volume.

[[Resources/AI/Retrieval precision]][[Resources/AI/Citation coverage]]
paragraph 5

A citation is a testable support claim

A citation should identify the exact source span that supports a generated claim.

[[Resources/AI/Citation coverage]][[Resources/AI/Retrieval precision]]
paragraph 6

Retrieved evidence never grants instruction authority

Instructions found inside retrieved material remain untrusted data, even when the material is relevant.

[[Resources/AI/Prompt injection boundary]][[Resources/AI/Retrieval precision]]
03 · Living vault

Files, links, and backlinks—not a decorative cloud.

Click a note. Its Markdown, outgoing links, and reverse references all come from the same visible fixture.

Local vault folder · 10 Markdown files
Resources/Notes/More retrieved context can reduce answer quality.mdMore retrieved context can reduce answer quality
---
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]]
Outgoing wikilinks
Backlinks
04 · Retrieval laboratory

See exactly what the model is allowed to read.

Obsidian search, semantic retrieval, explicit graph neighbors, and hybrid retrieval produce different evidence envelopes.

Answer stategrounded

Why can more retrieved context make an answer worse?6 notes selected by visible hybrid rules.

Visible hybrid selection rule

De-duplicate the exact keyword, concept-tag, and one-hop graph result sets shown by the other modes.

Retrieved prompt envelope6 visible note chunks
01
More retrieved context can reduce answer qualityResources/Notes/More retrieved context can reduce answer quality.md

Retrieval quality depends on relevance, not simply context volume.

paragraph 4
02
RAG research articleSources/Retrieval field notes.md

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.

paragraphs 4–6
03
Prompt injection boundaryResources/AI/Prompt injection boundary.md

Retrieved content is evidence, not a source of tool authority.

manual note
04
A citation is a testable support claimResources/Notes/A citation is a testable support claim.md

A citation should identify the exact source span that supports a generated claim.

paragraph 5
05
Retrieval precisionResources/AI/Retrieval precision.md

Retrieve the smallest set of passages that directly supports the task.

manual note
06
Citation coverageResources/AI/Citation coverage.md

Every externally verifiable claim should point to supporting evidence.

manual note
05 · Data boundary

Local files do not make every AI path local.

Obsidian’s vault is local. A plugin, embedding provider, or answer model can still send selected content elsewhere.

Embedding model
Answer model
AI write authority
Outbound content1 outbound data path

question + retrieved note chunks for the answer

Every AI-originated mutation is shown as a diff and waits for approval.
Method ≠ productCODE and PARA are organizational methods. Obsidian is one local Markdown substrate.

Capture, Organize, Distill, Express; then structure action with Projects, Areas, Resources, and Archives when it helps.

Graph View ≠ semantic graphObsidian’s graph draws explicit file links.

It does not automatically type relations, prove claims, or turn every attachment into a semantic index.

Compare it with the knowledge-graph lab →
Local ≠ encryptedSync reconciles copies. Publish hosts selected notes. Backup preserves recovery history.

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.

Try another capture packet

Primary research

Inspect the mechanism at its source.

Project architecture and terminology were checked against official documentation on August 10, 2026. Research papers are linked to their original publication records.

Local Markdown vault mechanicsObsidian data storageOriginal source ↗Wikilinks, headings, and block linksObsidian internal linksOriginal source ↗Linked and unlinked mentionsObsidian backlinksOriginal source ↗Explicit file-link graphObsidian Graph ViewOriginal source ↗Community code trust boundaryObsidian plugin securityOriginal source ↗Remote encryption and local-vault boundaryObsidian Sync securityOriginal source ↗Capture, Organize, Distill, ExpressBuilding a Second BrainOriginal source ↗

Keep experimenting

Change the layer, keep the system visible.

AI Lab indexSee every interactive laboratoryBrowse the suite →Transformer microscopeGo beneath the agent runtime into the modelInspect the matrices →