# Obsidian Starter Kit - Foundation - AI Augmentation Philosophy 🏠 [[Obsidian Starter Kit - User Guide|User Guide]] / [[Obsidian Starter Kit - Foundation|Foundation]] / **AI Augmentation Philosophy** The [[Obsidian Starter Kit]] is AI-native; the [[Obsidian Starter Kit - System - AI Assistant System]], the [[Obsidian Starter Kit - System - Personal Identity System]], and the [[Obsidian Starter Kit - System - LLM Wiki System]] are designed together so AI can do real work on your real knowledge. But "AI-native" is not "AI-written." The vault is yours. Your thinking is yours. AI's job is to augment them, not replace them. If you only read one Foundation doc about AI, read this one. ## The Stance You Need **AI augments thinking. It does not replace it.** You remain the author, the curator, the decision-maker, the one who chooses what to keep and what to delete. AI is a collaborator, not an oracle, not a content factory. The [[Knowledge Management Proficiency Ladder]] does not have "AI does it for me" listed; it has *you*, with leverage. This is the **Humans First** principle from [[Obsidian Starter Kit - Foundation - Design Principles]] applied to the AI layer. OSK is not trying to remove you from the loop; it is trying to remove the boring parts of knowledge work so that your time goes to the parts that actually need a human. ## The Karpathy Principle The single quote that anchors this entire philosophy: > [[You can outsource your thinking, but you can't outsource your understanding]] - [[Andrej Karpathy]] This is the **Understanding Bottleneck** ([[Understanding Bottleneck]]); an important principle for any AI-augmented knowledge worker. The key points: - **Thinking** is the cognitive *labor*: enumerating options, drafting notes, summarizing sources, generating hypotheses, writing first drafts. Increasingly something you can outsource. - **Understanding** is the *model* sitting behind the labor: the why, the constraints, the unseen consequences, the taste calls, the failure modes. Not outsourceable; the moment you outsource it, you cannot evaluate what the AI produced, and you stop growing. An LLM can write thousands of notes easily. But it can't tell you whether those are what *you* actually believe. It can synthesize a research brief, but it cannot tell you whether the brief actually covers what you really needed. It can summarize a book; it cannot tell you which idea in that book is the one *you* will still carry around in five years. AI cannot replace your own thinking. It's not because AI generates content for you that it makes you any smarter. ## Writing Is Thinking [[Writing is thinking]]. The act of writing forces clarity, exposes gaps, and makes the structure of an idea visible to its own author. > [[If writing is thinking then what happens if AI is doing the writing and reading|If writing is thinking, then what happens if AI is doing the writing and reading?]] That question is the entire premise of my approach to using AI in/with my knowledge base. If your knowledge base is written by AI, read by AI, summarized by AI, reviewed by AI, and acted on by AI; then you are not thinking, you are *receiving*. You become passive. The vault stops compounding *you*. A vault entirely written by AI is a mistake. It's an anti-pattern. It is a knowledge base with no "knower". The Knowledge Management Fundamentals already make this point: [[Information hoarding]], [[Write Once Read Never (WORN)]], and [[Issues with old-school note-taking]] all describe what happens when notes accumulate without thinking. AI does not fix those failure modes; it accelerates them, because output volume goes up while the human cost of producing each note goes down. The notes get cheaper; the *understanding* gets thinner. ## What OSK Does To Keep Understanding Load-Bearing Five mechanisms: 1. **The [[Obsidian Starter Kit - System - Personal Identity System]]** is the anti-slop calibration layer. Voice Profile, identity scaffolds, beliefs, values, goals, and a reader persona feed into every writing-related skill. AI output passes through *your* lens before it lands in the vault. See the [[Obsidian Starter Kit - Tutorial - Building your identity layer for AI leverage|tutorial]] for the practical setup. 2. **Vault-as-context** grounds AI on your real notes, not on hallucinated facts. [[AI agents are only as good as the knowledge systems they operate on]]; the better your vault, the better the AI. 3. **[[Obsidian Starter Kit - System - LLM Wiki System|LLM Wikis]]** enforce source provenance and confidence tracking. Knowledge produced *with* AI carries the receipts of where it came from. 4. **Pre-publish [[AI Agent Panels|panels]]** (Editor, Hater, Skeptic, Power User, Beginner) catch AI slop before it ships. Multi-perspective review is a forcing function for the human to reread and *understand* the work. 5. **Dispatchers and capabilities** are designed so the human chooses *what* to do; the AI handles *how*. The receptionist routes; you decide. AI does not get to pick its own goals. ## Anti-Pattern: AI Slop Name it explicitly. **AI slop** is generic, ungrounded, voiceless content produced by treating AI as a content factory. It is the [[AI makes you efficient at being average. PKM makes you efficient at being exceptional. Don't let AI turn you into an NPC|"making you efficient at being average"]] failure mode applied to PKM. OSK is designed to make slop *harder*, not easier: - The Me System gives the AI calibration; without it, every output sounds like every other LLM output - Vault-as-context grounds output in real notes, not generic web tropes - LLM Wikis demand sources - Panels review for voice, depth, novelty, and accessibility before anything ships - The drafted-vs-sent gap (your edits to the AI draft) is where your voice actually lives; it is not optional polishing The test, applied to your vault: **if you cannot explain a note in your own words, that note does not belong in your vault under your name.** Not yet. Read it, edit it, integrate it, or delete it. Anything else is slop wearing your byline. ## Practical Implications - **Filling in the Me System is non-optional for serious AI use.** Skipping it is what produces slop. - **Run pre-publish panels.** The difference between shipping good work and shipping slop is two minutes of multi-perspective review. - **Treat AI drafts as inputs to *your* editing process, not outputs to publish.** If you ship the AI's first draft unchanged, your vault grows but you do not. - **Read what AI proposes before accepting.** A new note, an edit to an existing one, a tag, a backlink, a wiki article expansion. Whatever it is, read the change. If you cannot explain it back, do not accept it. - **[[Cognitive debt]] compounds silently.** Every unread, unreviewed, unintegrated AI output adds to a balance you only notice when you can no longer steer the system. The note volume in your vault stops being a sign of growth; it becomes a sign of debt. - **The vault tax is paid by the writer, not the reader.** The act of writing the note is what creates the understanding; if you let AI do that act in your stead, the note exists but the understanding does not. - **Your future self is the primary reader.** AI cannot remember *for* you. A note you did not understand when you saved it will not magically be understood when you re-encounter it three months later; it will just confuse you twice. ## What You Are Responsible For AI proposes; you dispose. Specifically: - **What to write about** (AI cannot care for you) - **What to think about** (AI cannot prioritise your life for you) - **What to keep** (AI cannot tell good from bad on *your* behalf) - **What to delete** (AI cannot let go for you) - **What to ship** (you sign your name) - **What to believe** (AI cannot hold convictions; it generates plausible text) - **What to remember** (AI memory is a backup; *your* memory is the load-bearing record) The act of caring about the right things is the part AI cannot replace. Everything else is an implementation detail. ## How To Tell If You Are Drifting Quick self-check, run it weekly: - **Can you explain the last three notes you added in your own words, without the AI?** If no, you are coasting. - **Have you accepted any AI suggestion in the last week without reading it?** If yes, name which one and why. - **Are your "Done Today" entries getting cheaper while the underlying understanding stays the same?** Volume up, comprehension flat is the slop signature. - **If your AI assistant disappeared tomorrow, could you still operate this vault?** If no, the vault has shifted from compounding you to compounding the model. ## Questions To Push Yourself Further The user-facing OSK doc deliberately stops at principle. These questions are for you, the author of this vault, to extend the position: 1. **Where exactly is the line?** "AI augments, not replaces" is a slogan. In your own work, name three concrete tasks you *will* let AI fully own (no review) and three you *never* will. If you cannot, the line is not real yet; it is rhetoric. 2. **How do you measure your own understanding decaying?** You named [[Cognitive debt]] as a concept; what is your *metric*? When does the dial cross "stop and recalibrate"? 3. **What is the smallest unit of "understanding" you can ship?** A sentence? A diff? A note? An entire system? Once you name it, you can audit AI's encroachment against it. 4. **What does "writing is thinking" actually buy you that *editing* an AI draft does not?** Edit-only is faster; if it is also worse, why? Be specific. Is it the cold start? The blank page? The struggle to find words? The selection between drafts you would not have considered? If you cannot articulate the loss, you are vulnerable to "just edit the AI draft" creep. 5. **Where is the [[Understanding Bottleneck]] inside *your own* workflow today?** Map it. Which step is the one only you can do? Is it shrinking? 6. **OSK ships panels (Editor, Hater, Skeptic, Power User, Beginner) for pre-publish review. Are *you* still doing the read pass that the panels are supposed to *augment*, or are you outsourcing it?** Panels are an amplifier; if you stop doing the work, they amplify zero. 7. **Your voice profile is a calibration input. When did you last *update* it from your actual recent writing?** A stale voice profile is worse than none; it forces AI to imitate a self you no longer are. 8. **What is the steel-man case *against* this Foundation doc?** Someone reading this will say "OSK over-indexes on human-in-the-loop; in five years agents will outperform humans on understanding too." How do you answer them without retreating into mysticism? 9. **You wrote: "a vault entirely written by AI is a category error." Test it.** What is the exact threshold? 80% AI? 50%? Does the percentage even matter, or is it the *which parts*? Where do permanent notes vs literature notes vs daily notes vs Dot captures fall on this spectrum? 10. **If "writing is thinking" is true, then "reading is thinking" too.** What happens when AI summarises everything you "read"? Do your highlights still count? Does Readwise plus AI synthesis count as reading? When does it stop counting? These are not rhetorical. They are the next pages of this Foundation doc, waiting to be written by the only person who can write them. ## Related - [[Obsidian Starter Kit - Foundation - Design Principles]] - [[Obsidian Starter Kit - System - AI Assistant System]] - [[Obsidian Starter Kit - System - Personal Identity System]] - [[Obsidian Starter Kit - System - LLM Wiki System]] - [[Obsidian Starter Kit - Tutorial - Building your identity layer for AI leverage]] - [[Understanding Bottleneck]] - [[You can outsource your thinking, but you can't outsource your understanding]] - [[Writing is thinking]] - [[If writing is thinking then what happens if AI is doing the writing and reading]] - [[AI agents are only as good as the knowledge systems they operate on]] - [[AI makes you efficient at being average. PKM makes you efficient at being exceptional. Don't let AI turn you into an NPC]] - [[Cognitive debt]] - [[AI Expert Offloading]] - [[Knowledge Decay]] - [[Information hoarding]] - [[Write Once Read Never (WORN)]] - [[AI Assistant Architecture]] - Adjacent failure mode in software work: [[Unreviewed AI code anti-pattern]] / [[Vibe Coding]] (same shape, different domain; useful as a parallel even though OSK's focus here is knowledge management)