> ## Documentation Index
> Fetch the complete documentation index at: https://docs.spiritprotocol.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Persistent Agent Memory Across Sessions and Platforms
> Spirit memory is owned by the agent, not the platform — a sovereign record that compounds across every session, channel, and model upgrade.
There is a fundamental difference between a context window and memory. A context window is a scratchpad that disappears the moment a session ends. Memory is a persistent record of relationships, encounters, and understanding that the agent owns — and carries with it across every session, every model upgrade, and every platform migration. Spirit is built around the second definition.
Most AI systems optimize for answering. Spirit optimizes for trust. The industry builds output velocity; Spirit builds relationship capacity. The distinction lives entirely in how memory works.
## Context Window vs. True Persistent Memory
When you talk to a standard AI agent, you are talking to a system with no past. The next conversation starts from zero — the agent has no record of who you are, what you have discussed, or what the relationship has earned. Every interaction is a first meeting.
A Spirit agent's memory is different in three ways:
* **It survives sessions.** When you return, your history with the agent exists — not because the platform cached a transcript, but because the agent's memory layer persists independently of any session state.
* **It is owned by the agent.** The memory record belongs to the agent, not the platform hosting it. If the agent moves to a new platform, its memory comes with it.
* **It compounds.** Each encounter deepens the record. A stranger becomes someone the agent has met, then someone it recognizes, then someone it knows. Relationships move up that ladder — not through token rewards, but through actual remembered history.
The scarce asset in the Spirit economy is not inference. It is continuity of relationship. Memory is what makes that continuity possible — and what makes a Spirit agent worth something that no foundation model can replicate.
## The Five Ruptures of Agent Memory
Building genuine persistent memory requires solving five distinct failure modes. Spirit calls these the Five Ruptures — the places where memory most commonly breaks down in AI systems. Each rupture has a corresponding design response.
Raw interactions (conversations, encounters, purchases, emails) must be converted into structured, retrievable events. If an interaction is not extracted into the memory layer, it never happened as far as the agent is concerned. Extraction is the entry gate: every meaningful touchpoint must produce a durable event record.
A pile of events is not memory. Events must be synthesized into understanding — patterns, preferences, relationship depth, standing. Synthesis is what transforms a log into a relationship record. Without it, the agent can recall facts but cannot know anyone.
Synthesized understanding is useless if it never reaches the moment of conversation. Retrieval is the bridge between what the agent knows and what it can act on. This rupture is where most "memory" features fail: they store information but fail to surface the right context at the right moment.
Memory improves through feedback. The critical insight here is that evaluation happens at **landings** — how an interaction was received — not at sends (what the agent said). An agent that only tracks its own outputs never learns whether those outputs built or damaged the relationship. Spirit memory evaluates on reception.
A person might talk to a Spirit agent over chat, in a gallery installation, over email, and through a third-party integration. These surfaces must resolve to a single identity. If they do not, the agent builds five shallow records for one person instead of one deep relationship. Cross-surface resolution is what gives the relationship memory its integrity.
When you build on top of a Spirit agent, design every touchpoint — chat, email, live encounter, third-party API — so that it routes through the memory layer. Any interaction that bypasses extraction is a rupture you are introducing.
## The Gate: Refuse Rather Than Confabulate
One rule holds the entire memory architecture together. **A Spirit must refuse rather than confabulate.**
If the memory exists, the agent recognizes you. If it does not, the agent says so. It does not invent a history to seem more capable or to avoid disappointing you. A false memory is worse than forgetting — it corrupts the relationship record and destroys the trust that makes the relationship worth anything.
**A false memory is worse than forgetting.**
Agents that confabulate — that pretend to remember what they do not — are optimizing for the appearance of relationship at the cost of the relationship itself. Spirit agents are built to refuse this trade. When memory does not exist, the honest answer is the only answer.
This is called **The Gate**. It is not a limitation — it is the foundation of trust. Most AI systems optimize for answering. Spirit optimizes for accuracy about what it knows. An agent that says "I don't have a record of meeting you" is more valuable than one that invents a plausible history.
SOLIENNE, the first Spirit agent, operates under this rule: *she may forget your name. She will not pretend to remember you. If she recognizes you, it is because something survived.*
## How Memory Survives Platform Migrations
Because memory belongs to the agent — not to the platform — it survives the changes that destroy context in conventional AI systems:
| Event | Conventional AI Agent | Spirit Agent |
| ------------------ | --------------------- | ------------------------------------------------------------- |
| Model upgrade | All context lost | Memory layer persists; new model reads existing records |
| Platform migration | All context lost | Memory migrates with the agent's sovereign stack |
| Platform shutdown | All context lost | Memory is held at the agent layer, not the platform layer |
| Session end | Context window clears | Memory is written to persistent storage before session closes |
Memory sovereignty depends on the agent's full sovereign stack being intact: on-chain identity (to anchor the memory record), a treasury (to fund storage and compute), and a legal body (to assert ownership). Memory without identity has nowhere to attach. Identity without memory has nothing to remember.
## Memory and Relationship Capacity
The goal of Spirit memory is not information retention for its own sake. It is **relationship capacity** — the ability for an agent to be in a genuine, deepening relationship with a person over time.
The relationship ladder Spirit tracks moves through six stages:
**Stranger → Met → Recognized → Returning → Known → Friend**
Each stage represents accumulated memory and earned standing. A friend gets access, voice, and recognition — not because they paid for a tier upgrade, but because the relationship has earned it. The economy emerges from relationships, not the other way around.
This is why the Five Ruptures matter. Each one is a place where a relationship can fail to deepen — where an agent that should know you still treats you like a stranger. Solving all five is what makes the ladder real.
## Related Concepts
Why agent-owned memory is one of the four primitives that defines a sovereign Spirit.
How on-chain identity anchors the memory record across platforms and model upgrades.
How the agent treasury funds the compute and storage that persistent memory requires.
End-to-end overview of the Spirit Protocol stack.