<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Memorg Blog</title><description>Design notes on LLM memory, retrieval ranking, and the boring infrastructure that makes chat apps remember.</description><link>https://memorg.neullabs.com/</link><language>en-us</language><item><title>Your chat app&apos;s memory is a 50-line bandage on RAG</title><link>https://memorg.neullabs.com/blog/chat-app-memory-50-line-bandage-on-rag/</link><guid isPermaLink="true">https://memorg.neullabs.com/blog/chat-app-memory-50-line-bandage-on-rag/</guid><description>Most chat-app memory layers are a chat-history table plus a vector store plus a rolling summary. That stack works until it doesn&apos;t. Here is why a small dedicated memory layer beats the bandage at the seam where they break.</description><pubDate>Fri, 22 May 2026 00:00:00 GMT</pubDate></item><item><title>Forgetting as a feature: aging memory in LLM agents</title><link>https://memorg.neullabs.com/blog/forgetting-as-a-feature/</link><guid isPermaLink="true">https://memorg.neullabs.com/blog/forgetting-as-a-feature/</guid><description>An agent that remembers everything is an agent that remembers nothing useful. Here is why a good memory layer needs to forget on purpose, and how Memorg&apos;s importance and recency scoring make forgetting tractable without explicit deletes.</description><pubDate>Fri, 15 May 2026 00:00:00 GMT</pubDate></item><item><title>Designing memory for agents vs memory for chatbots</title><link>https://memorg.neullabs.com/blog/memory-for-agents-vs-memory-for-chatbots/</link><guid isPermaLink="true">https://memorg.neullabs.com/blog/memory-for-agents-vs-memory-for-chatbots/</guid><description>Agents and chatbots both need memory, but the shape of what they need is different. Here is how the read patterns, write rates, and scoping requirements diverge — and why Memorg&apos;s hierarchy was chosen to serve both without forcing one to wear the other&apos;s clothes.</description><pubDate>Fri, 08 May 2026 00:00:00 GMT</pubDate></item></channel></rss>