<?xml version="1.0" encoding="utf-8"?><rss version="2.0" xml:lang="en" xmlns:atom="http://www.w3.org/2005/Atom"><channel><link href="https://flowerinthenight.com/categories/memory/atom.xml" rel="self" type="application/atom+xml"/><link href="https://flowerinthenight.com/categories/memory/" rel="alternate" type="text/html"/><link href="https://flowerinthenight.com/categories/memory/rss.xml" rel="alternate" type="application/rss+xml"/><copyright>© Flowerinthenight, 2016-2026. All rights reserved.</copyright><description>Recent content</description><language>en</language><lastBuildDate>2026-07-12 00:00:00 +0900 JST</lastBuildDate><link>https://flowerinthenight.com/categories/memory/</link><managingEditor>root@flowerinthenight.com (Flowerinthenight)</managingEditor><title>Memory · Categories ·</title><webMaster>root@flowerinthenight.com (Flowerinthenight)</webMaster><item><description><![CDATA[<br>
<p>I&rsquo;ve been spending a lot of my nights and weekends on <a href="https://jennah.nightblue.io/">Jennah</a>. It kind of nagged its way into existence: AI agents are getting genuinely good, but the memory underneath them is still held together with tape. Everyone builds it the same way: a vector database for recall, a separate graph database for reasoning, an execution log off in the corner, and a pile of app-side glue trying to keep the three in sync. That&rsquo;s the thing I wanted to address. Jennah&rsquo;s whole idea is one store; execution logs, vector recall, and reasoning graphs living together in a single store per agent, instead of a vector DB bolted onto a graph DB bolted onto a log.</p>
<p>And because it&rsquo;s all in one place, I can commit a whole reasoning step atomically, then query across all of an agent&rsquo;s memory in a single request - semantic recall, graph reasoning, and recent history fused into one ranked, consistent answer, instead of me stitching three systems together and hoping they agree. And I wanted memory data to be consistent regardless of whether it&rsquo;s single region, multi-region (within a geography), or globally distributed. That&rsquo;s the part I keep geeking out over. The hard problem isn&rsquo;t storing any one kind of memory, it&rsquo;s making them behave as one. It&rsquo;s exactly the kind of thing I love as a CTO — unglamorous, foundational, the sort of problem that, if designed right, nobody ever has to think about again. Which is a weird thing to be excited about at 1am, but here we are.</p>
<p>More to come soon.</p>
<br>
<p>(If you&rsquo;re an investor in the space, you can contact me anytime.)</p>
<br>
]]></description><guid isPermaLink="false">tag:flowerinthenight.com,2026-07-12:/blog/2026-07-12-jennah-intro/</guid><link>https://flowerinthenight.com/blog/2026-07-12-jennah-intro/</link><pubDate>Sun, 12 Jul 2026 00:00:00 JST</pubDate><title>A little something I’ve been building</title></item></channel></rss>