> ## Documentation Index
> Fetch the complete documentation index at: https://docs.negentro.tech/llms.txt
> Use this file to discover all available pages before exploring further.

# Give your AI a memory that persists

> Memory lets your application retain useful information beyond a single request or session. Instead of treating every interaction as a blank slate, your system can refer to relevant facts, preferences, and decisions when they matter.

## What is persistent memory?

Persistent memory is information your application stores for potential future use. It may include user preferences, project context, recurring instructions, summaries, or facts extracted from previous interactions.

Memory is not the same as a complete conversation log. A well-designed memory system preserves information that has future value and makes it available when the application needs it.

## Core memory operations

> **store()**
>
> Save a new memory or piece of information for later retrieval.

> **retrieve()**
>
> Find existing memories relevant to a query, task, or user request.

> **update()**
>
> Revise stored information when it changes or becomes more precise.

> **delete()**
>
> Remove information according to user requests, retention rules, or application policy.

> **merge()**
>
> Combine overlapping or related information when consolidation is appropriate.

> **summarize()**
>
> Condense a larger body of information into a shorter representation for downstream use.

> **pin()**
>
> Mark selected information for special treatment, if supported by the configured implementation.

> **verify()**
>
> Check stored information against a defined source or validation process, where supported.

## A practical memory lifecycle

## What belongs in memory?

* Explicit user preferences.
* Long-running project decisions.
* Stable facts needed across sessions.
* Task state that must survive process restarts.
* Summaries of prior work that are relevant to future requests.

## Scope and ownership

Memory should be associated with a clearly defined owner and access scope. Your application should establish who can read, update, and delete each item, and ensure that one user's information cannot be retrieved by another without authorization.

## Memory quality

Persistent memory is only useful when it remains relevant and trustworthy. Establish rules for resolving conflicting facts, refreshing stale information, distinguishing user-provided facts from model-generated inferences, and honoring deletion requests.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.