Observed Signal · Aug 22, 2026 · Technical Release · Source: DEV Community · Impact: 2/5 · Sentiment: Positive
LLM Wiki: Protecting Human-Refined Notes with Curated Layer
The article describes agnosticBrain, a GitHub implementation that extends Andrej Karpathy's LLM Wiki pattern by adding explicit ownership layers to protect human-refined knowledge from being overwritten by LLM ingests. agnosticBrain defines directory-level ownership rules — including a read-only curated/ folder for human-canonical notes — and introduces workflows (/curate, /propose) so the LLM can propose diffs but never modify curated content without explicit human approval. The project documents nine kernel operations (AGENTS.md) and provides a proposal, logging, and index-based pipeline to close the learning loop while preserving manual edits.
Practical technical pattern and open-source implementation for protecting human-curated knowledge in LLM-driven knowledge bases; relevant to teams building LLM-assisted knowledge systems but not industry-shifting.
Track GitHub Signals & Market Shifts in Real-Time
Polaris7 autonomous intelligence agents track regulatory filings, primary sources, executive changes, and deal flow 24/7. Create your free Explorer workspace to monitor these entities.
Key Takeaways & Evidence Grounding
- Andrej Karpathy published his LLM Wiki gist in April 2026 proposing a compiled, persistent wiki maintained by an LLM.
- agnosticBrain (GitHub: Macorreag/agnosticBrain) extends the LLM Wiki pattern by introducing an explicit curated/ read-only layer to protect human-refined notes.
- agnosticBrain defines four directories with strict ownership rules: raw/ (human immutable), wiki/ (LLM-writable), curated/ (human-canonical, LLM never modifies), and archivo/ (system archive).
- The system implements workflows including /curate to freeze notes and /propose to have the LLM create diff proposals for curated notes; approval by a human is required to apply changes.
- The repository documents nine kernel operations (AGENTS.md) such as /ingest, /lint, /curate, /propose and /compose.
Connected Companies & Entities
5 Entities mapped“The article points readers to the full implementation hosted on GitHub: "If you want to see the complete implementation — with the 9 skills,...”
“The article frames Obsidian as the editor for the pattern: "Obsidian is the IDE, the LLM is the programmer, and the wiki is the code."...”
“The article notes the kernel file is read by agents and lists example agents: "...a file that is read without transformation by agents (Clau...”
“The article notes the kernel file is read by agents and lists example agents: "...a file that is read without transformation by agents (Clau...”
“The article notes the kernel file is read by agents and lists example agents: "...a file that is read without transformation by agents (Clau...”
Ontology Mapping & Concepts
Related Market Signals & Shifts
Recent verified developments and strategic activity across this market segment.
Karpathy's LLM Wiki: Guide to AI‑Maintained Knowledge Bases
This technical guide explains Andrej Karpathy's 'LLM Wiki' pattern — an LLM agent that builds and maintains a markdown knowledge base from immutable source files. The pattern uses a three-layer directory (raw/, wiki/, CLAUDE.md) and three core operations (ingest, query, lint). The article documents a complete setup using Claude Code and Obsidian, compares the approach to Retrieval‑Augmented Generation (RAG), lists community implementations that appeared within days, and surveys extensions (memory lifecycle, confidence scoring) and limitations (context-window degradation, model-collapse risk). It cites Karpathy's viral April 2026 post and related community projects and resources.
brain2.wiki: Cloud External Brain for LLM Wikis
brain2.wiki is a cloud-hosted "external brain" service that implements Karpathy-style LLM Wikis for long-term, agent-readable knowledge. The platform provides API-key authentication, UUID-isolated vaults, trigram full-text indexing, and an agent-first Skill that integrates with AI editors such as Cursor, Claude Code, and Trae. Workflows include local ingest into a raw/ layer, lint gates, manifest batch syncs to cloud vaults, and API-level single-page edits or exports. brain2.wiki also ships featured public vaults (Public Health Brain with 5,406 topics and Public Cooking Brain with 3,955 topics) that any registered agent can query. The design emphasizes durable, structured markdown pages, provenance metadata, and deterministic text search to let agents read, cite, and write enduring knowledge rather than relying on ephemeral chat logs.
Git-history Evidence Pack for LLM-powered Docs
The article describes a lightweight pipeline for producing LLM-drafted documentation grounded in a repository's git history. It provides a Python script that generates a "docs context pack" from recent commits, git blame, and common rationale markers, and prescribes a "drafting contract" that separates what a model may draft from what humans must own (notably rationale, security, and compliance). The author recommends strict model rules—cite commit hashes for historical claims, mark gaps as [UNVERIFIED], and never invent reasons—and a verification pass where humans resolve open questions. The piece notes MonkeyCode's free model access and server option (advertised 10M tokens at the time) as one implementation path. Publication date: 2026-08-29.
Track Real-Time Market Signals & Shifts
Set up custom watchlists to receive automated, evidence-grounded executive digests whenever material signals or shifts occur across your tracked landscape.