The Memory Files — Case 01: AI Memory 101
KingofKimchi's Substack
SubscribeSign in
The Memory Files — Case 01: AI Memory 101<br>Why Your AI Forgets (And What's Actually Going On In There)
KingofKimchi<br>Jul 02, 2026
Share
Part 1 of a series on AI memory — how it works, where it breaks, and why it's about to become one of the biggest fights in tech.<br>Quick gut check before we start: you’re already using AI for something in your business right now. An email draft. A customer reply. Maybe an actual tool you paid for that’s supposed to remember your clients so you don’t have to. You’ve probably never once asked what happens when it forgets. Most people don’t, until it costs them something — a customer quoted last month’s price instead of this month’s, a dead deal treated like it’s still live, your own AI flatly contradicting something it told your team yesterday. You don’t need to understand the plumbing to run a business. But you do need to understand this if you’re the one deciding how much to trust the AI already running parts of it.<br>The clearest way in is to start with what came before AI memory entirely — the plain, ordinary way computers have stored information for decades. Once you see what that looked like, it’s obvious exactly where AI breaks the pattern.<br>Picture a filing cabinet.<br>Traditional computer storage — your hard drive, a cloud drive like Google Drive or Dropbox, or if you’re old enough to remember burning one, a CD — is a giant, perfectly organized filing cabinet. Every piece of paper lives in a folder you put it in. You can find things fast if you know where you filed them. But the cabinet doesn’t understand anything on the page. It’s just really good storage.<br>Quick aside if you’re a Notion person: yes, it feels smarter than a plain filing cabinet — tags, databases, search that actually works. But structurally, it’s still storage, just with really good folder labels. It finds what you tell it to find. It doesn’t know what any of it means. Same cabinet, better handles.<br>AI memory is a different animal. It’s less a filing cabinet and more a friend who’s read every page in every folder and can instantly connect dots you didn’t even know were connectable. That’s the whole game — and it’s also exactly where things go wrong. Let’s slow way down and actually look inside.
What Is a “Context Pool”? (This Is the Part Everyone Skips)
Here’s the actual setup: before an AI answers your question, it doesn’t just start typing. It first goes and grabs a handful of relevant documents, brings them back to the table, and then answers you — using only what’s in its hands, plus what it already knew.<br>Picture that like a locked room. The AI is allowed to walk in, pull a few things off the shelf, and bring them back out. That room is the context pool .<br>That room only has what you put in it. It’s not the whole internet. It’s not everything the AI has ever seen. It’s a small, specific, curated pile of stuff — your documents, your notes, your company’s files — that got put there on purpose. “Closed” is the key word. Closed pool, not open ocean.<br>Every time you ask a question, the AI doesn’t dump the whole room on the table. It goes and finds the few things in that room actually relevant to your question. Which brings us to the next part — how does it know what’s relevant?<br>(One more thing, purely so you recognize it later: this whole setup has a technical name — Retrieval-Augmented Generation, or RAG. The acronym doesn’t matter. The room does.)
Semantic Search: Matching Meaning, Not Words
Old-school search matches keywords. Type “dog,” get results with the letters d-o-g in them. That’s it. That’s the whole trick.<br>Semantic search matches meaning. Here’s a concrete example:<br>You ask: “How do I stop losing money on late fees?”<br>The AI scores every document in the context pool for how close in meaning it is to your question — not how many words match. Say the pool has three documents:<br>A note that says “Customer canceled service after getting hit with a surprise late charge.” → Similarity score: 0.89 (very close in meaning, even though not one word matches your question)
A note that says “Customer loved the blue packaging.” → Similarity score: 0.04 (basically unrelated)
A note that says “Late payment penalty structure needs revisiting.” → Similarity score: 0.91 (extremely close in meaning)
Notice — your question never used the words “penalty,” “surprise charge,” or “packaging.” Doesn’t matter. Semantic search isn’t playing word-match. It’s asking “how close is this idea to that idea,” and handing you a number between 0 and 1 for every single comparison. Closer to 1 means more relevant. That number is the score.<br>Here’s the catch nobody mentions: basic semantic search is time-blind . A note from three years ago and a note from three minutes ago can score the exact same 0.91 if they mean the same thing — the system has no built-in sense that one of them is stale and one of them is a live instruction someone just gave....