<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Be better]]></title><description><![CDATA[Be better]]></description><link>https://singhapps.hashnode.dev</link><image><url>https://cdn.hashnode.com/res/hashnode/image/upload/v1593680282896/kNC7E8IR4.png</url><title>Be better</title><link>https://singhapps.hashnode.dev</link></image><generator>RSS for Node</generator><lastBuildDate>Fri, 11 Sep 2026 07:15:58 GMT</lastBuildDate><atom:link href="https://singhapps.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[From Context to Memory: Why the Next Generation of AI Needs to Remember
]]></title><description><![CDATA[How trying to build a "smart" medical record system completely changed our view of artificial intelligence.
A few months ago, we started building what we thought was a straightforward project: an AI s]]></description><link>https://singhapps.hashnode.dev/from-context-to-memory-why-the-next-generation-of-ai-needs-to-remember</link><guid isPermaLink="true">https://singhapps.hashnode.dev/from-context-to-memory-why-the-next-generation-of-ai-needs-to-remember</guid><category><![CDATA[#ai-tools]]></category><category><![CDATA[Cognee]]></category><category><![CDATA[LivingRecord]]></category><category><![CDATA[thehangoverai]]></category><category><![CDATA[hackathon]]></category><category><![CDATA[@WeMakeDevs @hashnode]]></category><category><![CDATA[WeMakeDevs]]></category><category><![CDATA[ai memory]]></category><category><![CDATA[AI memory companion]]></category><category><![CDATA[llm]]></category><category><![CDATA[ollama]]></category><category><![CDATA[openai]]></category><category><![CDATA[knowledge graph]]></category><category><![CDATA[large language models]]></category><category><![CDATA[Artificial Intelligence]]></category><category><![CDATA[Memory-Centric-ai]]></category><category><![CDATA[context engineering]]></category><category><![CDATA[ontology]]></category><category><![CDATA[Future of AI]]></category><category><![CDATA[Retrieval-Augmented Generation]]></category><category><![CDATA[Retrieval-Augmented Generation (RAG)]]></category><category><![CDATA[Human Cognition]]></category><dc:creator><![CDATA[Roshan]]></dc:creator><pubDate>Sun, 05 Jul 2026 19:38:00 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6a4aa64282a91c3e7c3a1b18/0dd2abb1-dbd9-418c-82ad-368af7134291.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p><em>How trying to build a "smart" medical record system completely changed our view of artificial intelligence.</em></p>
<p>A few months ago, we started building what we thought was a straightforward project: an AI system that could track a patient’s medical history across multiple reports. At first, we assumed the challenge was extracting data from PDFs. Then, we thought it was about choosing the right language model. We were wrong every single time.</p>
<p>The real challenge turned out to be something much more fundamental: <strong>How do you teach an AI to remember?</strong></p>
<p>We don't mean storing files on a disk or keeping a conversation inside a massive context window. We mean remembering the way a human does. When you visit your doctor, they don’t reread your entire chart from birth; they have a mental picture of your health, and today’s appointment simply updates that picture. Most AI systems, however, treat every interaction as a fresh start—like meeting a stranger for the first time, every single time.</p>
<h2><strong>A Question That Kept Getting Bigger</strong></h2>
<p><em>Moving from document-centric thinking to knowledge-centric understanding.</em></p>
<p>The deeper we went into our project, the more we asked ourselves: if humans build understanding through experience, why do AI systems keep starting over?</p>
<p>That question led us down a rabbit hole of cognitive science, knowledge graphs, and ontologies. Our healthcare project stopped being just about medicine; it became an exploration of memory itself. We realized that most AI conversations focus on making models larger or faster, while far too few ask whether the model is actually learning anything from yesterday.</p>
<p><strong>Living Record Note</strong></p>
<p>One of the first surprises we encountered was that simply storing more medical reports didn't make the AI any smarter. It just gave the model more text to search through. The patient wasn't being better understood; the system was simply accumulating documents.</p>
<h2><strong>What Is Memory, Really?</strong></h2>
<p><strong>Human Memory vs Today's AI Context</strong></p>
<ul>
<li><em>Humans build understanding over time. Most AI systems build answers one prompt at a time.</em></li>
</ul>
<img src="https://cdn.hashnode.com/uploads/covers/6a4aa64282a91c3e7c3a1b18/f26e1cd9-d2eb-459f-9057-36e8f50d112b.png" alt="" style="display:block;margin:0 auto" />

<p><em>Why memory is an evolving model of the world, not a filing cabinet.</em></p>
<p>Most of us equate memory with storage. But think back to your first day at a new job. Everything was overwhelming. Months later, you intuitively know where bugs hide in the code and who to ask for help. You didn't just "store" more data; you built a mental model.</p>
<p>Human memory is a web of connected experiences. We don't replay video archives; we organize life into coherent pictures. When we realized this, our approach to our prototype shifted: we stopped trying to make the AI store every report and started trying to make it refine an existing understanding.</p>
<p><strong>Key takeaway</strong></p>
<p>Memory isn't about storing more information. It's about continuously refining understanding.</p>
<h2><strong>Why Context Isn't Enough</strong></h2>
<p><strong>Context Window vs Long-Term Memory</strong></p>
<ul>
<li><em>Both use past information—but only one preserves and evolves it.</em></li>
</ul>
<img src="https://cdn.hashnode.com/uploads/covers/6a4aa64282a91c3e7c3a1b18/9bf3b046-73d0-4c43-a958-ad059f6decf9.png" alt="" style="display:block;margin:0 auto" />

<p><em>Why a massive context window is like a giant desk that gets cleared every night.</em></p>
<p>Modern models can read hundreds of pages, which is a massive leap forward. But a large context window is temporary. It is like a desk covered in papers—the larger the desk, the more you can spread out. But when you finish your work, the desk is cleared.</p>
<p>Context helps an AI think in the moment, but memory helps an AI grow over time. Providing more reports in a context window helped with one-off answers, but the system wasn't becoming "smarter" about the patient; it was just reading more documents each time.</p>
<h2><strong>Search Finds, Memory Builds</strong></h2>
<p><em>Understanding the limitations of RAG (Retrieval-Augmented Generation).</em></p>
<p>RAG is a powerful tool. It allows an AI to "walk into a library" and find the right book. It is efficient and solves the "knowledge cutoff" problem.  </p>
<p><strong>Search Finds Information. Memory Builds Understanding</strong></p>
<ul>
<li><em>Both retrieve knowledge—but only one continuously learns from new experiences.</em></li>
</ul>
<img src="https://cdn.hashnode.com/uploads/covers/6a4aa64282a91c3e7c3a1b18/6671161f-1b45-4f0f-bf09-19da8fea86a2.png" alt="" style="display:block;margin:0 auto" />

<p>However, search doesn't learn. If you search for the same information every day, you aren't an expert—you're just an efficient researcher.</p>
<p>For our medical project, retrieval was only half the battle. We needed the system to connect events across years, not just find the reports that mentioned them. We needed an evolving memory, not just a better search engine.</p>
<h2><strong>How Humans Build Memories</strong></h2>
<p><em>Lessons from the brain: connecting, filtering, and evolving.</em></p>
<p>If we want AI to remember, we should look at the only system that has been refining it for millions of years:</p>
<ul>
<li><p><strong>We connect, we don't categorize:</strong> Like meeting a new business partner who happens to work with an old friend, our brains link new information to existing mental nodes.</p>
</li>
<li><p><strong>Forgetting is a feature:</strong> We filter out the noise. AI needs to learn how to identify what deserves to become "long-term knowledge."</p>
</li>
<li><p><strong>Intuition is condensed experience:</strong> An expert doctor isn't "searching" a database; they are recognizing patterns built over years.</p>
</li>
</ul>
<p><strong>How Humans Build Lasting Understanding</strong></p>
<ul>
<li><em>Knowledge isn't accumulated one fact at a time—it emerges from connecting many experiences.</em></li>
</ul>
<img src="https://cdn.hashnode.com/uploads/covers/6a4aa64282a91c3e7c3a1b18/3ba122b5-152a-4b81-b726-b48a1381eb69.png" alt="" style="display:block;margin:0 auto" />

<p><strong>Living Record Note</strong></p>
<p>This was our biggest breakthrough. Once we stopped thinking in terms of documents and started thinking in terms of people, our design choices became obvious. Reports became experiences; the patient became the memory.</p>
<h2><strong>What Would AI Memory Actually Look Like?</strong></h2>
<p><em>Defining the characteristics of a memory-driven architecture.</em></p>
<p>If we were to design an AI memory from scratch, it should:</p>
<ol>
<li><p><strong>Recognize the same thing twice:</strong> It should know that "John Doe" in report A is the same "John" in report F.</p>
</li>
<li><p><strong>Connect, don't collect:</strong> It should see the relationship between a symptom, a medication, and a lab result.</p>
</li>
<li><p><strong>Evolve:</strong> It should understand that a patient's story changes.</p>
</li>
<li><p><strong>Explain itself:</strong> It should show the "path" that led to a conclusion, moving away from "black box" behavior.</p>
</li>
</ol>
<h2><strong>Building Living Memory</strong></h2>
<p><strong>Memory-Centric AI Architecture</strong></p>
<ul>
<li><em>From raw documents to an evolving knowledge graph that continuously improves understanding.</em></li>
</ul>
<img src="https://cdn.hashnode.com/uploads/covers/6a4aa64282a91c3e7c3a1b18/01c0be88-67c3-4f54-9276-e3bd33f383a9.png" alt="" style="display:block;margin:0 auto" />

<p><em>Moving from document-centric to entity-centric architectures.</em></p>
<p>The shift to entity-centric architecture was our "aha!" moment. Instead of the PDF being the center of the universe, the entities (Patient, Medication, Diagnosis) became the anchors. We used ontologies to give the AI a shared language, ensuring that "Type 2 Diabetes" and "elevated blood sugar" are understood as the same concept.</p>
<p>By building a knowledge graph, we created a living representation that extends, refines, and corrects itself with every new interaction. During this process, we found a framework called <a href="https://github.com/topoteretes/cognee"><strong>Cognee</strong></a>, whose philosophy closely aligned with the architectural direction our own thinking had taken—treating AI memory as a dedicated layer that grows alongside the language model.</p>
<h2><strong>A Living Medical Record</strong></h2>
<p><em>The proof of concept.</em></p>
<p>When a new report arrived, we didn't add it to a stack; we used it to update the patient's story. We could ask the AI, "How has John's diabetes changed over three years?" The system didn't just retrieve files; it reasoned over the timeline of relationships.</p>
<p>Time became part of the knowledge. A diagnosis isn't meaningful without knowing <em>when</em> it happened; a medication only makes sense if you know whether it's still active. That single word—<em>changed</em>—is where memory becomes essential.</p>
<ul>
<li><em>Each medical encounter adds to an evolving understanding rather than becoming another isolated PDF.</em></li>
</ul>
<p><strong>A Living Medical Record</strong></p>
<img src="https://cdn.hashnode.com/uploads/covers/6a4aa64282a91c3e7c3a1b18/58800d5f-8a2e-42ad-93e5-4a4f7d42e262.png" alt="" style="display:block;margin:0 auto" />

<h2><strong>Beyond Healthcare</strong></h2>
<p><em>The universal pattern of knowledge.</em></p>
<p>The problem we solved wasn't medical—it was structural. Everywhere we looked, we found the same pattern:</p>
<ul>
<li><p><strong>Education:</strong> A tutor that remembers your struggles with fractions.</p>
</li>
<li><p><strong>Software:</strong> An assistant that knows why a piece of code was written a certain way three years ago.</p>
</li>
<li><p><strong>Enterprise:</strong> Organizational knowledge that stays when employees leave.</p>
</li>
</ul>
<p><strong>Beyond Healthcare: Where Living Memory Can Make a Difference</strong></p>
<img src="https://cdn.hashnode.com/uploads/covers/6a4aa64282a91c3e7c3a1b18/d4b661c3-dc22-486a-982e-b64346746d28.png" alt="" style="display:block;margin:0 auto" />

<ul>
<li><em>Any domain where understanding evolves over time can benefit from memory-centric AI.</em></li>
</ul>
<p>This isn't just a feature; it's the foundation for AI that feels like a collaborator rather than a tool.</p>
<h2><strong>The Next Frontier of Artificial Intelligence</strong></h2>
<p><em>Looking forward to AI that lives through experiences.</em></p>
<p>We are still in the early days of memory-centric AI. There are challenges with privacy, scalability, and long-term evaluation. But every major AI breakthrough started with someone asking a different question. We stopped asking "How can this model store more?" and started asking "How can this model learn from what it has already seen?"</p>
<p>What do you think? Is long-term memory one of the missing pieces in today's AI systems, or do you believe larger models and longer context windows will eventually be enough? We'd genuinely love to hear your perspective—after all, every good conversation leaves us with something worth remembering.</p>
<p><em><strong>The Evolution Toward Memory-Centric AI</strong></em></p>
<img src="https://cdn.hashnode.com/uploads/covers/6a4aa64282a91c3e7c3a1b18/a00b2cae-0f3c-42ef-ab90-f5b057a26685.png" alt="" style="display:block;margin:0 auto" />

<ul>
<li><em>Each step builds upon the previous one, bringing AI closer to continuous understanding rather than isolated responses.</em></li>
</ul>
]]></content:encoded></item></channel></rss>