• Another Tutorial, Same Broken Record: A Technical Rebuttal
  • 1. "The LLM remembers everything you did years ago"
  • 2. "Graphify implements everything Karpathy talked about"
  • 3. "Very simple, very effective, not heavy"
  • 4. "The graph HTML gives you connections you probably didn't know"
  • 5. "Keep on compounding. It will keep on evolving over time."
  • 6. "You can run queries against the graph JSON"
  • 7. No mention of the fundamental problems
  • The actual video
  • The Bottom Line
  • ⚠️ THE WORD "WIKI" HAS BEEN PERVERTED ⚠️
• Related pages

Another Tutorial, Same Broken Record: A Technical Rebuttal

This video presents Graphify as an implementation of Karpathy’s LLM-Wiki pattern. Let me point out what the video gets wrong — or conveniently leaves out.

---

1. “The LLM remembers everything you did years ago”

Claim: “Years later, you still can query everything. The system kept everything that you did and the LLM kept building the information in a very structured way.”

Reality: The LLM has no persistent memory across sessions. It forgets everything between chats. The only “memory” is the markdown files and JSON graphs it wrote last time. If those files contain errors, contradictions, or hallucinations, the LLM will confidently repeat them. The system does not “remember.” It stores. And storage without integrity is just a landfill.

---

2. “Graphify implements everything Karpathy talked about”

Claim: “It implemented everything that Karpathy talked about.”

Reality: Graphify adds a knowledge graph layer with entity extraction, relationship detection, and community clustering. That’s not “everything Karpathy talked about.” That’s a significant extension. Karpathy’s original pattern is just markdown files with wikilinks. Graphify is doing graph database work — which is good — but the video presents it as a simple implementation of the original pattern. It’s not. It’s a different architecture.

---

3. “Very simple, very effective, not heavy”

Claim: “Very simple, very effective, it’s not heavy.”

Reality: Graphify uses entity extraction, relationship detection, community clustering, and graph generation. That’s computationally heavy. The demo works with 4 small text files. At scale, with hundreds of PDFs, images, and videos, these operations are not “not heavy.” They are expensive in both compute and API tokens. The video never shows the cost or the time required for large-scale ingestion.

---

4. “The graph HTML gives you connections you probably didn’t know”

Claim: “This is something that you probably didn’t know but just looking at the files. It understands it through the Graphify process.”

Reality: The LLM extracts entities and relationships based on pattern matching and its training data. These “surprising connections” might be genuine insights, or they might be hallucinations. The video presents them as discoveries without any validation step. There is no mechanism to verify that a detected relationship actually exists in the source documents. The user is left trusting the LLM’s output.

---

5. “Keep on compounding. It will keep on evolving over time.”

Claim: “This is keep on compounding. After you put more files in this raw folder, it’s going to keep on involving over time.”

Reality: Compounding requires integrity. Without foreign keys, without version control, without contradiction resolution, without permission management, the system does not compound — it accumulates. Accumulation without integrity is noise. The video shows a graph of 4 communities from 4 small text files. It does not show what happens after 100 files, when entities multiply, relationships overlap, contradictions emerge, and the graph becomes uninterpretable.

---

6. “You can run queries against the graph JSON”

Claim: “You can run query against it. This is the part you use the query for.”

Reality: The video shows a graph JSON file. It does not show what query language you use. It does not show the query syntax. It does not show how to ask “show me all documents related to entity X” or “find contradictions between source A and source B.” The viewer is left to assume that querying is easy. It is not specified.

---

7. No mention of the fundamental problems

The video never addresses:

Missing	Why It Matters
What happens at 1,000 files?	The index breaks. You need vector search.
Who verifies entity extractions?	The LLM might hallucinate relationships.
How do you resolve contradictions?	The graph will show conflicting relationships.
How do you handle permissions?	The LLM sees everything.
What is the API cost at scale?	Not mentioned.
How do you version the graph?	Not mentioned.
How do you roll back incorrect extractions?	Not mentioned.

---

The actual video

The Bottom Line

Graphify is a nice project. It adds entity extraction and graph visualization to Karpathy’s pattern. That is genuinely useful for small-scale knowledge exploration.

But the video presents it as a complete solution that “compounds over time” and “remembers everything.” It does not. The LLM forgets between sessions. The graph has no integrity guarantees. The system has no permissions. The cost at scale is ignored. The human still has to validate every extraction, every relationship, every “surprising connection.”

The video is a tutorial for a prototype that works with 4 small text files. It is not a blueprint for a production knowledge base. The sheep are still lining up. 🐑💀

Build a real knowledge base. Use PostgreSQL. Add foreign keys. Implement permissions. Track versions. Extract metadata deterministically. Let the LLM assist — not replace. 🧙🐘

⚠️ THE WORD “WIKI” HAS BEEN PERVERTED ⚠️

Related pages

• Shepherd's LLM-Wiki vs. Robust Dynamic Knowledge Repository: A Satirical Allegory on AI-Generated Knowledge Management
  This satirical allegory critiques the trend of relying on Large Language Models (LLMs) to automatically generate and manage knowledge bases using simple Markdown files, portraying this approach as a naive "Shepherd's" promise that inevitably leads to data inconsistency, hallucinations, privacy leaks, and unmanageable maintenance. The text contrasts this fragile, probabilistic "LLM-Wiki" method with a robust, 23-year-old "Dynamic Knowledge Repository" (DKR) built on structured databases (like PostgreSQL) and Doug Engelbart's CODIAK principles, arguing that true knowledge management requires human curation, deterministic relationships, and explicit schemas rather than blindly following AI-generated text files.
• Karpathy's LLM-Wiki Is a Flawed Architectural Trap
  The author sharply criticizes Andrej Karpathy's viral "LLM-Wiki" concept as a flawed architectural trap that mistakenly treats unstructured Markdown files as a robust database, arguing that relying on LLMs to autonomously generate and maintain knowledge leads to hallucinations, broken links, privacy leaks, and a loss of human cognitive engagement. While acknowledging the appeal of compounding knowledge, the text asserts that Markdown lacks essential database features like referential integrity, permissions, and deterministic querying, causing the system to collapse at scale and contradicting its own "zero-maintenance" promise. Ultimately, the author advocates for proven, structured solutions using real databases and human curation, positioning LLMs as helpful assistants rather than autonomous masters, and warns against blindly following a trend promoted by someone who has publicly admitted to being in a state of psychosis.
• Critical Rebuttal to LLM-Wiki Video: Why Autonomous AI Claims Are Misleading
  The text provides a critical rebuttal to a video promoting "LLM-Wiki," arguing that the system’s claims of autonomous intelligence, zero maintenance costs, and scalability are fundamentally misleading. The critique highlights that LLMs lack persistent memory, leading to repeated errors, while the system’s actual intelligence is merely increased data density rather than genuine understanding. Furthermore, the video ignores significant practical challenges such as substantial API costs, the inevitable need for embeddings at scale, the complexity of fine-tuning, and the persistent human labor required for data integrity and contradiction resolution. Ultimately, the author concludes that the video is merely a tutorial for a fragile prototype that fails to address critical issues like version control, access management, and long-term viability.
• The LLM-Wiki Pattern: A Flawed and Misleading Alternative to RAG
  The text is a scathing critique of the "LLM-Wiki" pattern, arguing that its claims of being a free, embedding-free alternative to RAG are technically flawed and misleading. The author contends that the system inevitably requires vector search and local indexing tools (like qmd) to scale, fundamentally contradicting the "no embeddings" premise, while also failing to preserve source integrity by retrieving from hallucinated LLM-generated summaries rather than original documents. Furthermore, the approach is deemed unsustainable due to hidden API costs, the inability of LLMs to maintain large indexes beyond small prototypes, and the lack of essential database features like foreign keys and version control, ultimately positioning it as a fragile prototype rather than a viable production knowledge base.
• Why LLM-Based Wiki Systems Are Flawed and Unscalable
  The text serves as a technical rebuttal to popular tutorials promoting LLM-based wiki systems, arguing that these prototypes are fundamentally flawed and unscalable. The author contends that such systems lack persistent memory, rely on hallucinated summaries that corrupt original data, and fail at scale due to context window limits and the need for embeddings despite claims otherwise. Furthermore, the approach is criticized for being token-expensive, lacking proper data integrity measures like foreign keys or permissions, and fostering "self-contamination" through unverified LLM suggestions. Ultimately, the author advises against adopting this "trap" as a knowledge base solution, recommending instead robust, traditional database architectures like PostgreSQL with deterministic metadata extraction, while dismissing the hype as an appeal to authority that ignores broken architecture.
• LLM Wiki vs RAG: Why RAG Wins for Production Despite LLM Wiki's Knowledge Graph Appeal
  While a recent video by "Data Science in your pocket" offers a balanced comparison between LLM Wiki and RAG by highlighting LLM Wiki’s ability to build structured, reusable knowledge graphs versus RAG’s repetitive, stateless retrieval, it ultimately fails to address critical production flaws. The author argues that LLM Wiki is currently a fragile prototype rather than a robust architecture, lacking essential database features like foreign keys, referential integrity, access controls, and deterministic metadata extraction. Consequently, while LLM Wiki may suit personal knowledge building, its susceptibility to error propagation, high maintenance costs, and lack of true memory make RAG the superior choice for reliable, production-ready systems, with a hybrid approach recommended for optimal results.
• Why LLM Wiki Fails as a RAG Replacement: Context Limits and Data Integrity Issues
  The text serves as a technical rebuttal to a video claiming that "LLM Wiki" renders Retrieval-Augmented Generation (RAG) obsolete, arguing instead that LLM Wiki is merely a rebranded, less robust version of RAG that fails at scale due to context window limitations and lacks true persistent memory or data integrity. The author highlights that LLM Wiki relies on static markdown files which cannot enforce database constraints, resolve contradictions, or prevent hallucinations from becoming "solidified" errors, ultimately requiring the same search mechanisms and human maintenance that RAG avoids. The conclusion emphasizes that while context engineering is valuable, it should be supported by proper databases with foreign keys and version control rather than fragile markdown repositories, urging developers to use LLMs as tools for processing rather than as the foundation for knowledge storage.
• Critique of LLM Wiki Tutorial: Limitations and Production Readiness
  The technical evaluation critiques the LLM Wiki tutorial for misleading claims that AI eliminates maintenance friction and provides persistent memory, revealing instead that the system relies on static markdown files with no referential integrity, privacy controls, or error-checking mechanisms. While the video correctly advocates for separating raw sources from generated content and using schema files, it critically omits essential issues such as hallucination propagation, silent link breakage, lack of version control for individual facts, scaling limits requiring RAG, and ongoing API costs. Ultimately, the tutorial is deemed suitable only as a small-scale personal prototype requiring active human supervision, rather than a robust, production-ready knowledge base.
• LLM Wiki vs Notebook LM: Hidden Costs Privacy Tradeoffs and the Hybrid Approach
  This video offers a rare, honest side-by-side evaluation of LLM Wiki and Notebook LM, correctly highlighting LLM Wiki’s significant hidden costs—including slow ingestion times, high token usage, and poor scalability beyond ~100 sources—while acknowledging Notebook LM’s speed and ease of use. However, the review understates critical privacy and ownership trade-offs, specifically that Notebook LM processes data on Google’s servers (posing risks for sensitive information) and lacks user control, whereas LLM Wiki’s maintenance burden is the price for local data sovereignty. Ultimately, the creator recommends a pragmatic hybrid approach: using Notebook LM for quick exploration and LLM Wiki for deep, long-term academic research, emphasizing that the goal should be actionable knowledge rather than just building a wiki.
• Debunking Karpathy's LLM Wiki: The Truth Behind the Self-Healing Marketing Hype
  The video is a heavily hyped marketing pitch for Karpathy’s "LLM Wiki" that misleadingly claims the system is "self-healing" and autonomous, while in reality, it relies on static files, requires significant human intervention for maintenance, and lacks true memory or self-correction capabilities. The presentation ignores critical technical limitations such as token costs, scale constraints beyond ~100 sources, privacy risks, and the potential for hallucinations, ultimately presenting a flawed RAG-based solution as a revolutionary upgrade without acknowledging its trade-offs or the substantial effort required to keep it functional.
• LLM Wiki Pattern: A Balanced Review Highlighting Limitations and Operational Challenges
  This video provides a balanced and honest introduction to the "LLM Wiki" pattern, correctly identifying its limitations to personal scales (100–200 sources) and acknowledging that RAG remains superior for larger datasets. While it avoids the hype and sales tactics of other videos by clearly explaining the system’s transparency, portability, and immutable source practices, it significantly understates critical operational challenges. The review notes that the video fails to address essential practical issues such as token costs, lengthy ingest times, the human maintenance burden required to resolve contradictions and broken links, and privacy concerns, making it a good conceptual overview but insufficient for understanding the full technical and financial realities of implementation.
• Why LLM Wiki Is a Bad Idea: A Critical Analysis of Flaws and RAG Alternatives
  The video "Why LLM Wiki is a Bad Idea" provides a strong, technically accurate critique of the LLM Wiki approach, correctly identifying eight major flaws including error propagation, structured hallucinations, information loss, update rigidity, and scalability issues, while recommending a hybrid RAG-based system. Although it overstates the difficulty of updates by implying full graph rebuilds and unfairly ignores RAG’s own costs and hallucination risks, it remains the most direct and valuable critical resource for understanding the significant pitfalls of relying solely on LLM-generated structured knowledge bases.
• Why Adam's LLM Wiki in Business Implementation Fails as a Production Framework
  Adam’s "LLM Wiki in Business" implementation fundamentally fails as a production framework because it exhibits every critical flaw identified in the opposing critique, including error propagation, hallucination structuring, information loss, and a lack of provenance or security. By relying on unstructured folders and rigid JSON schemas instead of a proper database with foreign keys, audit trails, and scalable retrieval mechanisms, Adam’s system violates all four essential pillars of reliable knowledge management (Store, Relate, Trust, Retrieve) and admits its own inability to scale beyond a small number of clients. Consequently, the analysis concludes that Adam’s approach is not a superior alternative to RAG, but rather an unintentional case study demonstrating why LLM Wiki is a flawed and risky strategy for business applications requiring accuracy, security, and scalability.
• Critical Evaluation of Local LLM Wiki with Obsidian: Fundamental Flaws and Business Unsuitability
  The evaluation concludes that the "Local LLM Wiki with Obsidian" tutorial fails all four fundamental pillars of a robust knowledge base—Store with Integrity, Relate with Precision, Trust with Provenance, and Retrieve with Speed—due to its reliance on unstructured markdown files lacking foreign keys, immutability, typed relationships, audit trails, and queryable SQL capabilities. Although the creator is praised for intellectual honesty and transparency about the prototype’s limitations, the architecture remains fundamentally flawed, and the use of proprietary software (Obsidian) introduces critical risks including vendor lock-in, telemetry concerns, zero access control, and the absence of multi-user support, rendering it unsuitable for any business, collaborative, or sensitive use cases despite its appeal as a personal hobby tool.
• James' LLM Wiki Fails Robust Knowledge Management Due to Lack of Database Integrity
  The evaluation concludes that while James from Trainingsites.io offers a rare, pragmatic, and honest assessment by correctly distinguishing between using an LLM Wiki for personal organization and RAG for customer-facing queries, his implementation fundamentally fails the four pillars of robust knowledge management: Store with Integrity, Relate with Precision, Trust with Provenance, and Retrieve with Speed. By relying on proprietary Obsidian and markdown files rather than a real database, his system lacks foreign keys, immutability, provenance tracking, access controls, and queryability, making it structurally unsound for professional or collaborative use despite its effectiveness as a personal browsing tool.
• Memex: Advanced LLM Wiki with Critical Database Limitations
  Memex is a sophisticated LLM Wiki implementation that stands out for its thoughtful mitigations of common pitfalls, such as git-backed versioning, inline citation tracking, provenance dashboards, and contradiction policies. However, despite being the most advanced attempt in this space, it fundamentally fails the "Four Pillars" of a proper knowledge base because it relies on markdown files rather than a relational database. This architectural choice results in critical limitations: it lacks foreign keys (leading to broken citations on renames), has no permissions or access control, supports only text data, and provides non-deterministic, LLM-mediated retrieval instead of precise SQL queries. Consequently, while Memex is an excellent personal research tool, it is not production-ready for collaborative, secure, or enterprise use cases that require data integrity and structured querying.