LLM Wikis and the Hidden Risk of Flattened Permissions
Краткое содержание
Pixel shares why team LLM wikis can flatten access controls when agents compile sources into shared pages. Using examples like HR files, customer escalations, and board notes, the announcement explains why derived facts inherit the sensitivity of their most restricted source and why citations alone cannot protect confidential information.
DEV Community
Your LLM Wiki Compiles Away Your Permissions. Design for It Before the Team Uses It.
A short thread on X last week put the LLM wiki vs. RAG debate better than most long posts do: a wiki compiles knowledge when a source arrives; RAG retrieves at question time, so per-user permissions and citations stay intact. That line matters most to people taking the trending personal second-brain setups to their team. And right now a lot of people are. Karpathy's LLM Wiki idea file, Garry Tan's open-sourced gbrain, and the Claude Code + Obsidian vault repos are being cloned by the thousand. They work well for one person, because one person has one permission level: everything. The trouble starts when the same pattern is pointed at a shared drive with HR folders, customer escalations, and board notes in it. This post is about that one gap. It's not a case against LLM wikis. I think they are the right shape for a lot of team knowledge. But the compile step quietly erases your access model unless you design for it. Why compiling flattens permissions In the LLM wiki pattern, raw sources stay immutable and an agent writes a linked set of markdown pages that summarize, cross-reference, and update as new sources land. You get answers that are already synthesized, instead of re-deriving them from chunks on every query. Now picture the page the agent writes for a customer: a public case study (everyone can read it) a sales call note (sales team only) a legal escalation about a contract dispute (legal and two execs) The agent does what it was asked and writes a good page: "Acme: renewal at risk; dispute over SLA credits; legal involved since October." That page now holds facts from the most restricted source, and it sits in a folder whose permissions were set for the least restricted one. Citations don't fix this. Even if the page links back to a source the reader can't open, the reader has already read the sentence. A derived fact inherits the sensitivity of its most sensitive input, and a compiled page is made of derived facts. RAG with permission-aware retrieval doesn't have this failure mode, because it filters source passages per user before generation. What it gives up is the compounding synthesis that makes a wiki useful. You don't have to pick one. You do have to decide, page by page, where the access check happens. Rule 1: a page's audience is the intersection of its sources' audiences The simplest rule that holds up: the agent may only write a page into a scope that every source used for that page is visible to. In set terms, the page's allowed readers are the intersection of each source's allowed readers. Make it machine-checkable. Put the sources in frontmatter: ---
title: "Acme account summary"
scope: sales
sources:
- id: case-study-acme-2025
acl: [everyone]
- id: call-note-2026-10-02
acl: [sales]
- id: legal-escalation-114
acl: [legal, exec]
Then refuse the write when the declared scope is broader than what the sources allow: EVERYONE = "everyone"
def allowed_readers(sources, groups):
"""Intersect source ACLs. 'everyone' expands to all known groups."""
result = set(groups)
for s in sources:
acl = set(groups) if EVERYONE in s["acl"] else set(s["acl"])
result &= acl
return result
def check_page(page, groups):
readers = allowed_readers(page["sources"], groups)
if page["scope"] not in readers:
raise PermissionError(
f"{page['title']}: scope '{page['scope']}' exceeds sources; "
f"allowed: {sorted(readers) or 'nobody'}"
)
groups = {"sales", "legal", "exec", "eng", "people"}
The Acme page above fails: sales ∩ {legal, exec} is empty.
When the intersection comes back empty, that's useful information. It means the page shouldn't exist as one page. Split it: a sales-scoped summary that leaves out the escalation, and a legal-scoped page that adds it. Agents are good at writing two versions. They are bad at guessing which version you meant. Run this check in the agent's write path, not as a nightly lint. By the time a nig...

Powered by Readybot.io