# Consolidation (/docs/memory/intelligence/consolidation)
A long-running assistant collects thousands of small details: every login, every ticket update, every passing remark. Most stop mattering, but they still crowd out the memories that do. Consolidation keeps a memory space lean by folding old details into summaries.

<Callout type="info" title="Consolidation helps most when...">
- Your app captures many small events about the same people or accounts.
- Recall results are filling up with old, repetitive details.
</Callout>

## How it works [#how-it-works]

1. **Find candidates.** Docklee looks for memories that are at least 14 days old and have dropped in relevance.
2. **Group them.** Candidates are grouped by the entities they share. A group needs at least 3 memories.
3. **Summarize.** Each group becomes one summary memory that keeps the facts that matter.
4. **Keep the originals.** The originals are kept for 30 days after the summary is made, so nothing is lost by mistake.

Consolidation runs in the background. It never runs during a capture or a recall.

## What stays in full [#what-stays-in-full]

Some memories are never summarized, however old they are.

| Kept in full | Why |
| --- | --- |
| Policies, decisions, and constraints | They define how your app should behave. |
| The only memory about an entity | Summarizing it would lose the entity. |
| Memories confirmed by several sources | They're the most trusted facts you have. |
| Frequently recalled memories with high confidence | They're still in use. |
| Memories flagged for review | A person hasn't decided on them yet. |
| Memories set to keep forever | You chose to keep them. See [Retention](/docs/memory/governance/retention). |
| Memories under a legal hold | They can't be changed. See [Legal hold](/docs/memory/governance/legal-hold). |

## An example [#an-example]

| Before | After |
| --- | --- |
| "Omar logged in from Chrome." | |
| "Omar logged in from Safari." | One summary: "Omar signs in regularly, from both Chrome and Safari." |
| "Omar logged in on Monday morning." | |
| "Omar's contract renews on 1 June." | Kept in full, because it's the only memory about the renewal. |

## In the dashboard [#in-the-dashboard]

A summary appears as one memory in the memory space. Open it to see the originals it was built from, for as long as they're kept.

## Next steps [#next-steps]

Old details stay out of the way. See how recall chooses what to return next.

<Cards>
  <Card title="Ranking" href="/docs/memory/intelligence/ranking" description="The signals behind every recall." />
  <Card title="Retention" href="/docs/memory/governance/retention" description="Keep memories forever, or for a set time." />
  <Card title="Memory types" href="/docs/memory/memory-types" description="Which types are summarized first." />
</Cards>
