<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
        xmlns:image="http://www.google.com/schemas/sitemap-image/1.1">
  <url>
    <loc>https://octamem.com/</loc>
    <image:image>
      <image:loc>https://octamem.com/brand/opengraph-image.png</image:loc>
      <image:title>OctaMem — persistent memory platform for AI agents</image:title>
      <image:caption>OctaMem social card: the enterprise memory platform giving AI agents persistent semantic, episodic, and procedural memory across sessions.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://octamem.com/brand/octamem-logo.svg</image:loc>
      <image:title>OctaMem logo</image:title>
      <image:caption>The OctaMem brand mark — an interlocking eight-fold figure representing the memory graph that links records across connected sources.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/news/octamem-joins-nvidia-inception</loc>
    <image:image>
      <image:loc>https://octamem.com/brand/nvidia-inception-lockup.svg</image:loc>
      <image:title>OctaMem is a member of the NVIDIA Inception program</image:title>
      <image:caption>NVIDIA Inception program lockup shown on the announcement that OctaMem, the AI memory platform, joined NVIDIA&apos;s program for AI startups.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/desktop/ingestion-app</loc>
    <image:image>
      <image:loc>https://octamem.com/desktop/overview.webp</image:loc>
      <image:title>OctaMem desktop app memory dashboard</image:title>
      <image:caption>The OctaMem desktop application on macOS showing the Overview dashboard with active memory records, API request volume, and connector status.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://octamem.com/desktop/sources.webp</image:loc>
      <image:title>Connecting memory sources in the OctaMem desktop app</image:title>
      <image:caption>The Sources screen of the OctaMem desktop app, where Google Drive, OneDrive, GitHub, Outlook, and Teams are connected as memory sources and sync frequency is set.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://octamem.com/desktop/activity.webp</image:loc>
      <image:title>OctaMem memory activity and audit log</image:title>
      <image:caption>The Activity view in the OctaMem desktop app listing every memory read and write with its scope, source document, and timestamp for audit.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://octamem.com/desktop/injection-file.webp</image:loc>
      <image:title>OctaMem Ingestion adding file memory to a prompt</image:title>
      <image:caption>OctaMem Ingestion attaching file-based memory context to a prompt so an assistant answers from the organisation&apos;s own documents.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/desktop/application</loc>
    <image:image>
      <image:loc>https://octamem.com/download/desktop-app.webp</image:loc>
      <image:title>Download the OctaMem desktop app</image:title>
      <image:caption>The OctaMem desktop application download screen for macOS and Windows, used to connect local and cloud sources to the memory layer.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/benchmarks</loc>
    <image:image>
      <image:loc>https://octamem.com/benchmarks/locomo-overview-v2.webp</image:loc>
      <image:title>OctaMem LoCoMo benchmark results 2026 — 93.51% accuracy</image:title>
      <image:caption>Summary of OctaMem&apos;s 2026 LoCoMo benchmark run: 93.51% accuracy across 1,540 questions, the six capabilities the benchmark measures, and the cost per question.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/docs/openclaw</loc>
    <image:image>
      <image:loc>https://octamem.com/docs/integrations/openclaw.webp</image:loc>
      <image:title>OctaMem and OpenClaw agent memory integration</image:title>
      <image:caption>Co-branded OctaMem and OpenClaw graphic for the guide on installing OctaMem as an OpenClaw plugin so agents persist memory between runs.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/docs/claude-desktop</loc>
    <image:image>
      <image:loc>https://octamem.com/docs/integrations/claude.webp</image:loc>
      <image:title>OctaMem and Claude Desktop memory integration over MCP</image:title>
      <image:caption>Co-branded OctaMem and Claude Desktop graphic for the guide on connecting OctaMem as a Model Context Protocol server so Claude can remember, recall, and forget.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/docs/cursor</loc>
    <image:image>
      <image:loc>https://octamem.com/docs/integrations/cursor.webp</image:loc>
      <image:title>OctaMem and Cursor memory integration</image:title>
      <image:caption>Co-branded OctaMem and Cursor graphic for the guide on adding OctaMem as an MCP server in Cursor so project context survives editor sessions.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/docs/tutorials/crewai-memory</loc>
    <image:image>
      <image:loc>https://octamem.com/docs/integrations/crewai.webp</image:loc>
      <image:title>OctaMem and CrewAI shared crew memory</image:title>
      <image:caption>Co-branded OctaMem and CrewAI graphic for the tutorial on backing a CrewAI crew&apos;s ExternalMemory with OctaMem so agents share memory across runs.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/blog</loc>
    <image:image>
      <image:loc>https://octamem.com/blog/covers/mem0-vs-zep-vs-octamem.webp</image:loc>
      <image:title>Mem0 vs Zep vs OctaMem: choosing an AI agent memory layer</image:title>
      <image:caption>The Mem0, Zep, and OctaMem logos on three pedestals around a central VS marker, illustrating a comparison of the three AI agent memory layers.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://octamem.com/blog/covers/types-of-ai-agent-memory.webp</image:loc>
      <image:title>The 4 types of AI agent memory: semantic, episodic, procedural &amp; working</image:title>
      <image:caption>Four cards around the OctaMem mark showing the memory types: semantic (general knowledge and facts), episodic (events, experiences and context), procedural (skills, routines and how-to knowledge), and working (current context and active reasoning).</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://octamem.com/blog/covers/add-persistent-memory-to-cursor-and-claude.webp</image:loc>
      <image:title>How to add persistent memory to Cursor and Claude (MCP)</image:title>
      <image:caption>Cursor and Claude connected through MCP to OctaMem, the persistent memory layer, giving both tools long-term memory across sessions.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/blog/deal-file-should-answer-back</loc>
    <image:image>
      <image:loc>https://octamem.com/blog/covers/deal-file-should-answer-back.webp</image:loc>
      <image:title>The deal file should answer back</image:title>
      <image:caption>Four steps around the OctaMem mark: upload the deal file in any format, OctaMem analyses and structures the key information, ask questions in natural language, and get accurate answers with references back to the deal file.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/blog/matter-memory-without-breaking-walls</loc>
    <image:image>
      <image:loc>https://octamem.com/blog/covers/matter-memory-without-breaking-walls.webp</image:loc>
      <image:title>Matter memory without breaking matter walls</image:title>
      <image:caption>Four panels around the OctaMem mark: secured document storage, linked records under lock, reasoning over the matter, and improving outcomes — memory that respects client and matter boundaries.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/blog/best-enterprise-ai-memory-platforms</loc>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/best-enterprise-ai-memory-platforms.webp</image:loc>
      <image:title>Quadrant map of thirteen AI memory products, plotted by whether they are infrastructure you assemble or a memory layer you adopt, and whether self-hosting is available. Purpose-built memory layers sit right, cloud platform services bottom, storage infrastructure left.</image:title>
      <image:caption>Position reflects what each product ships today, not what it could be built into. The right-hand column is the only one selling memory as the product.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/best-enterprise-ai-memory-platforms-mem0.webp</image:loc>
      <image:title>The Mem0 homepage, headlined &quot;AI memory that persists across sessions and agents&quot;, with a Python quickstart showing MemoryClient.</image:title>
      <image:caption>Mem0 leads with a drop-in SDK and a generous free tier.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/best-enterprise-ai-memory-platforms-zep.webp</image:loc>
      <image:title>The Zep homepage, headlined &quot;Agent memory, at enterprise scale&quot;, showing a memory graph visualisation in the product dashboard.</image:title>
      <image:caption>Zep builds a temporal knowledge graph and is the one competitor here already holding SOC 2 Type II.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/best-enterprise-ai-memory-platforms-letta.webp</image:loc>
      <image:title>The Letta documentation homepage, describing the platform for building stateful agents that learn from experience.</image:title>
      <image:caption>Letta comes out of the MemGPT research line: memory blocks the agent edits itself.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/best-enterprise-ai-memory-platforms-cognee.webp</image:loc>
      <image:title>The Cognee homepage, headlined &quot;Open Source Memory Platform for Agents&quot;, offering Slack, GitHub and Linear connections.</image:title>
      <image:caption>Cognee is the most open of the memory layers, and prices on tokens processed.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/best-enterprise-ai-memory-platforms-supermemory.webp</image:loc>
      <image:title>The Supermemory documentation homepage, describing context infrastructure for AI agents with developer platform, plugins and MCP, and self-hosting sections.</image:title>
      <image:caption>Supermemory sells context infrastructure with an unusually explicit rate card.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/best-enterprise-ai-memory-platforms-bedrock.webp</image:loc>
      <image:title>AWS documentation page for adding memory to a Bedrock AgentCore agent, with a diagram contrasting agents without memory and agents with memory enabled.</image:title>
      <image:caption>AgentCore Memory splits short-term session context from long-term extraction, and is framework-agnostic.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/best-enterprise-ai-memory-platforms-vertex.webp</image:loc>
      <image:title>Google Cloud documentation for the Gemini Enterprise Agent Platform, listing Agent Runtime, Sessions, Memory Bank and Code Execution.</image:title>
      <image:caption>Google splits state into Sessions for the current conversation and Memory Bank for persistent long-term memories.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/best-enterprise-ai-memory-platforms-azure.webp</image:loc>
      <image:title>The Microsoft Foundry product page, describing a unified platform for app development with agents, models and tools.</image:title>
      <image:caption>Foundry gives agents persistent threads. Threads are conversation state, not a memory layer.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/best-enterprise-ai-memory-platforms-pinecone.webp</image:loc>
      <image:title>The Pinecone homepage, headlined &quot;Give agents knowledge&quot;, describing a knowledge platform for AI agents.</image:title>
      <image:caption>Pinecone now markets itself as giving agents knowledge — still a vector database underneath.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/best-enterprise-ai-memory-platforms-weaviate.webp</image:loc>
      <image:title>The Weaviate homepage, headlined &quot;Design, build and ship complete AI experiences&quot;, covering vector search, RAG and memory.</image:title>
      <image:caption>Weaviate is open source and self-hostable, which is why it appears in on-prem memory builds.</image:caption>
    </image:image>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/best-enterprise-ai-memory-platforms-redis.webp</image:loc>
      <image:title>The Redis homepage, headlined &quot;Inquiring agents want to know&quot;, showing an agent memory and context retrieval demo.</image:title>
      <image:caption>Redis is the usual home for short-term agent state, and increasingly markets vector search too.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/blog/why-does-my-ai-keep-forgetting</loc>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/why-does-my-ai-keep-forgetting.webp</image:loc>
      <image:title>A chat window is a bucket, not a brain. When it fills, the oldest context falls out. A shared memory sits outside the bucket and keeps what the team learned.</image:title>
      <image:caption>A chat window is a bucket, not a brain. When it fills, the oldest context falls out. A shared memory sits outside the bucket and keeps what the team learned.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/blog/what-is-a-company-brain</loc>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/what-is-a-company-brain.webp</image:loc>
      <image:title>Sources on the left, people and AI agents on the right, one governed memory in the middle. Every answer carries the source it came from.</image:title>
      <image:caption>Sources on the left, people and AI agents on the right, one governed memory in the middle. Every answer carries the source it came from.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/blog/can-law-firms-use-chatgpt-safely</loc>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/can-law-firms-use-chatgpt-safely.webp</image:loc>
      <image:title>What a defensible AI setup needs. A public chatbot fails most of the list. A governed memory with matter walls and an audit log passes it.</image:title>
      <image:caption>What a defensible AI setup needs. A public chatbot fails most of the list. A governed memory with matter walls and an audit log passes it.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/blog/law-firm-institutional-memory-when-a-partner-leaves</loc>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/law-firm-institutional-memory-when-a-partner-leaves.webp</image:loc>
      <image:title>The documents stay when a partner leaves. Almost everything that made the documents useful goes with them.</image:title>
      <image:caption>The documents stay when a partner leaves. Almost everything that made the documents useful goes with them.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/blog/ai-for-real-estate-agents-brokerages-2026</loc>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/ai-for-real-estate-agents-brokerages-2026.webp</image:loc>
      <image:title>The point tool tax. Every AI tool an agent uses knows nothing about the others, so the agent becomes the memory that connects them.</image:title>
      <image:caption>The point tool tax. Every AI tool an agent uses knows nothing about the others, so the agent becomes the memory that connects them.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/blog/real-estate-deal-memory-hold-period</loc>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/real-estate-deal-memory-hold-period.webp</image:loc>
      <image:title>Knowledge leaks at every handoff in the hold period. A deal memory keeps lender terms, diligence and rationale attached to the asset from acquisition to exit.</image:title>
      <image:caption>Knowledge leaks at every handoff in the hold period. A deal memory keeps lender terms, diligence and rationale attached to the asset from acquisition to exit.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/blog/how-to-start-an-ai-native-company</loc>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/how-to-start-an-ai-native-company.webp</image:loc>
      <image:title>A five person AI native company. The memory sits in the middle. Founders, contractors and agents all work from it, and everything they produce feeds back into it.</image:title>
      <image:caption>A five person AI native company. The memory sits in the middle. Founders, contractors and agents all work from it, and everything they produce feeds back into it.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/blog/how-to-start-an-ai-native-real-estate-company</loc>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/how-to-start-an-ai-native-real-estate-company.webp</image:loc>
      <image:title>Three ways to build an AI native property business. The tools differ. The memory underneath them is the same.</image:title>
      <image:caption>Three ways to build an AI native property business. The tools differ. The memory underneath them is the same.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/blog/best-tools-to-build-an-ai-startup-2026</loc>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/best-tools-to-build-an-ai-startup-2026.webp</image:loc>
      <image:title>The 2026 stack in layers. Most founders pick the top and bottom layers in a week. The memory layer is the one that decides whether the AI on top knows anything about the company.</image:title>
      <image:caption>The 2026 stack in layers. Most founders pick the top and bottom layers in a week. The memory layer is the one that decides whether the AI on top knows anything about the company.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/blog/ask-your-codebase-questions-founder</loc>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/ask-your-codebase-questions-founder.webp</image:loc>
      <image:title>The codebase holds more than code. Every commit is a decision, every change has a reason, and most of it never reaches the founder.</image:title>
      <image:caption>The codebase holds more than code. Every commit is a decision, every change has a reason, and most of it never reaches the founder.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/blog/connect-github-to-ai-memory</loc>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/connect-github-to-ai-memory.webp</image:loc>
      <image:title>From repositories to answers. GitHub is read continuously, turned into typed memory next to the rest of the company&apos;s knowledge, and asked from the tools you already use.</image:title>
      <image:caption>From repositories to answers. GitHub is read continuously, turned into typed memory next to the rest of the company&apos;s knowledge, and asked from the tools you already use.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/blog/onboard-developers-contractors-codebase-memory</loc>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/onboard-developers-contractors-codebase-memory.webp</image:loc>
      <image:title>Onboarding without memory is three weeks of interrupting the one person who knows. With memory it is a day of asking, and the answers come with sources.</image:title>
      <image:caption>Onboarding without memory is three weeks of interrupting the one person who knows. With memory it is a day of asking, and the answers come with sources.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/blog/coding-agents-forget-codebase-memory</loc>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/coding-agents-forget-codebase-memory.webp</image:loc>
      <image:title>A session index knows what the code is. A durable memory knows why. The coding agent needs both, and so does everyone else in the company.</image:title>
      <image:caption>A session index knows what the code is. A durable memory knows why. The coding agent needs both, and so does everyone else in the company.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/blog/open-source-ai-winning-founders-2026</loc>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/open-source-ai-winning-founders-2026.webp</image:loc>
      <image:title>Model orchestration. A router sends routine work to a fast, cheap open model and escalates the hard cases to a frontier model. Both draw on the same company memory.</image:title>
      <image:caption>Model orchestration. A router sends routine work to a fast, cheap open model and escalates the hard cases to a frontier model. Both draw on the same company memory.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/blog/open-source-ai-memory-problem</loc>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/open-source-ai-memory-problem.webp</image:loc>
      <image:title>The model layer commoditised. The memory layer did not. Six failure modes of self built memory, and what a governed layer adds.</image:title>
      <image:caption>The model layer commoditised. The memory layer did not. Six failure modes of self built memory, and what a governed layer adds.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/blog/cursor-permissions-json-mcp-allowlist</loc>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/cursor-permissions-json-mcp-allowlist.webp</image:loc>
      <image:title>Three sources of permissions and the strict order Cursor applies them in.</image:title>
      <image:caption>Three sources of permissions and the strict order Cursor applies them in.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/blog/what-is-an-ai-memory-layer</loc>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/what-is-an-ai-memory-layer.webp</image:loc>
      <image:title>The four operations of a memory layer. Most systems ship write and retrieve only.</image:title>
      <image:caption>The four operations of a memory layer. Most systems ship write and retrieve only.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/blog/coala-cognitive-architectures-language-agents</loc>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/coala-cognitive-architectures-language-agents.webp</image:loc>
      <image:title>CoALA&apos;s taxonomy, and the category error it leaves unresolved.</image:title>
      <image:caption>CoALA&apos;s taxonomy, and the category error it leaves unresolved.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/blog/ai-memory-layer-cost</loc>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/ai-memory-layer-cost.webp</image:loc>
      <image:title>Five pricing models and what each one couples your bill to.</image:title>
      <image:caption>Five pricing models and what each one couples your bill to.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/blog/semantic-memory-in-ai-agents</loc>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/semantic-memory-in-ai-agents.webp</image:loc>
      <image:title>Supersession keeps the current truth and the audit trail at the same time.</image:title>
      <image:caption>Supersession keeps the current truth and the audit trail at the same time.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/blog/episodic-memory-in-ai-agents</loc>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/episodic-memory-in-ai-agents.webp</image:loc>
      <image:title>Episodic retrieval that ranks on four signals instead of one.</image:title>
      <image:caption>Episodic retrieval that ranks on four signals instead of one.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/blog/procedural-memory-in-ai-agents</loc>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/procedural-memory-in-ai-agents.webp</image:loc>
      <image:title>Explicit procedural memory can be governed. Implicit cannot.</image:title>
      <image:caption>Explicit procedural memory can be governed. Implicit cannot.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/blog/agent-memory-benchmarks-explained</loc>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/agent-memory-benchmarks-explained.webp</image:loc>
      <image:title>What the three benchmarks grade, and the shared blind spot.</image:title>
      <image:caption>What the three benchmarks grade, and the shared blind spot.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/blog/how-to-choose-an-ai-memory-layer</loc>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/how-to-choose-an-ai-memory-layer.webp</image:loc>
      <image:title>The ten tests, weighted. Run the critical three for your sector first.</image:title>
      <image:caption>The ten tests, weighted. Run the critical three for your sector first.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/blog/agent-memory-failure-modes</loc>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/agent-memory-failure-modes.webp</image:loc>
      <image:title>Nine production failure modes. Eight share one root cause.</image:title>
      <image:caption>Nine production failure modes. Eight share one root cause.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/blog/gdpr-right-to-erasure-ai-memory</loc>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/gdpr-right-to-erasure-ai-memory.webp</image:loc>
      <image:title>Deletion removes the episodes. The summary they fed survives.</image:title>
      <image:caption>Deletion removes the episodes. The summary they fed survives.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/blog/mcp-memory-servers</loc>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/mcp-memory-servers.webp</image:loc>
      <image:title>One memory server behind every MCP client.</image:title>
      <image:caption>One memory server behind every MCP client.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/blog/context-engineering-vs-memory</loc>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/context-engineering-vs-memory.webp</image:loc>
      <image:title>The boundary contract: memory ranks, context engineering selects and shapes.</image:title>
      <image:caption>The boundary contract: memory ranks, context engineering selects and shapes.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/blog/law-firm-organisational-intelligence</loc>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/law-firm-organisational-intelligence.webp</image:loc>
      <image:title>The law firm memory problem</image:title>
      <image:caption>The same knowledge, held in people versus held by the firm.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/blog/real-estate-organisational-intelligence</loc>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/real-estate-organisational-intelligence.webp</image:loc>
      <image:title>Deal memory across the property lifecycle</image:title>
      <image:caption>A deal generates knowledge at every stage. Almost none of it survives the deal.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/blog/organisational-intelligence-universal-brain</loc>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/organisational-intelligence-universal-brain.webp</image:loc>
      <image:title>Fragmented context versus a governed universal brain</image:title>
      <image:caption>Left: every person feeds every agent by hand, and nothing persists. Right: people and agents share one governed memory that compounds.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/blog/company-brain-for-startups</loc>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/company-brain-for-startups.webp</image:loc>
      <image:title>Founder as context bottleneck versus a shared company brain</image:title>
      <image:caption>Without a brain, every agent&apos;s context routes through a founder. With one, context is written once and retrieved everywhere.</image:caption>
    </image:image>
  </url>
  <url>
    <loc>https://octamem.com/blog/second-brain-for-ai-agents</loc>
    <image:image>
      <image:loc>https://octamem.com/blog/figures/second-brain-for-ai-agents.webp</image:loc>
      <image:title>One personal memory serving every agent</image:title>
      <image:caption>Vendor-locked memories keep your context in silos. A personal memory layer makes it portable.</image:caption>
    </image:image>
  </url>
</urlset>
