Blog
Notes from the Statewave project
How agent memory works under the hood, deployment patterns we land on, and the design choices behind a Postgres-only, self-hosted memory runtime. Subscribe via RSS.
- memoryepisodic-memorysemantic-memoryagent-memory
Episodic vs Semantic Memory in AI Agents: What to Store and When
Episodic memory stores what happened; semantic memory stores what's true. Here's how AI agents use each, when to convert one to the other, and how to store it.
Read post
- provenanceauditcompliancearchitecture
Agent memory provenance: why your LLM app needs an audit trail
When an AI agent answers from memory, you need to know where it learned the answer. This post explains the provenance model in Statewave — what we store, what it costs, and what it enables for compliance, debugging, and trust.
Read post
- memoryragarchitecture
AI agent memory vs RAG — what's the difference?
Retrieval-augmented generation and an agent memory runtime overlap at the embedding store, but they answer different questions. Here's where the two diverge and which to reach for.
Read post
- supporttutorialmemory
How to add persistent memory to your AI support agent
A practical walkthrough of giving a support agent durable memory of customers across sessions — what to record, how to compile it, how to retrieve it, and what to expect from the support workflow benchmark.
Read post
- postgrespgvectordeploymentself-hosted
Self-hosted AI memory with Postgres and pgvector
Why Statewave is Postgres-only by design, what pgvector buys you over a dedicated vector database, and what the deployment shape looks like in production.
Read post