
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Rambling Me</title>
      <link>https://www.rambling-me.com/blog</link>
      <description>A blog to reflect my thoughts, learnings, and observations</description>
      <language>en-us</language>
      <managingEditor>me@rambling-me.com (Dopeking)</managingEditor>
      <webMaster>me@rambling-me.com (Dopeking)</webMaster>
      <lastBuildDate>Wed, 16 Sep 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.rambling-me.com/tags/memory/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.rambling-me.com/blog/posts/technology/agentic/operating-at-scale/1-memory-is-a-system</guid>
    <title>Agentic Systems: Memory Is a System, Not a Prompt Trick</title>
    <link>https://www.rambling-me.com/blog/posts/technology/agentic/operating-at-scale/1-memory-is-a-system</link>
    <description>&quot;Give it more context&quot; is the default answer to every memory problem in an agentic system, and it is not a memory architecture. Cost grows with length, relevance decays, and nothing survives the session. Separating the four stores that get collapsed into the word memory - working context, the ledger, derived state, and retrieval - and what each one is actually for.</description>
    <pubDate>Wed, 16 Sep 2026 00:00:00 GMT</pubDate>
    <author>me@rambling-me.com (Dopeking)</author>
    <category>technology</category><category>agentic</category><category>multi-agent-systems</category><category>memory</category><category>state</category><category>data-architecture</category><category>practitioner</category>
  </item>

    </channel>
  </rss>
