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

# Memory review and cleanup

> Review Memory, Directives, Episodes, Knowledge Graph, and Analytics so Sofie stays aligned with your work.

Review personalization periodically so Sofie does not carry stale assumptions into new work. Memory and Directives are useful when they are current, specific, and appropriate for future conversations.

Use this guide when you are cleaning up old Memory, checking Directive behavior, or preparing Sofie for a new project or role.

## When to review

Review Memory and Directives when:

* You move to a new role, project, product, site, or function.
* A Workspace or project closes.
* Sofie starts making assumptions that no longer fit.
* You see duplicate or vague memories.
* You created many Memories while exploring a temporary topic.
* You are starting source-heavy regulated or quality work.

## Review the tabs

The Memories page can include several tabs.

| Tab                 | What to check                                                 |
| ------------------- | ------------------------------------------------------------- |
| **Memories**        | Stored facts and preferences Sofie may use later.             |
| **Directives**      | Standing rules Sofie should follow.                           |
| **Episodes**        | Interaction history views when available.                     |
| **Knowledge Graph** | Connections among remembered concepts when available.         |
| **Analytics**       | Memory usage, sources, and retrieval patterns when available. |

<Note>
  Availability can vary by organization and feature settings.
</Note>

## Clean up Memory

<Steps>
  <Step title="Open Memories">
    Open **Manage Memory** and stay on the **Memories** tab.
  </Step>

  <Step title="Search by project or topic">
    Search for product names, project names, departments, sites, or recurring workflow terms.
  </Step>

  <Step title="Check content">
    Confirm each Memory is stable, useful, and appropriate for future conversations.
  </Step>

  <Step title="Check type and importance">
    Make sure **Type** and **Importance** match how much the Memory should influence Sofie.
  </Step>

  <Step title="Edit or delete">
    Edit vague Memory. Delete stale, duplicated, temporary, or sensitive Memory.
  </Step>
</Steps>

Delete Memory that looks like:

* `Today I am reviewing the deviation packet.`
* `The root cause is operator error.`
* `Use the old acceptance criteria from last year.`
* `Always answer with maximum detail.`
* `This one meeting had a disagreement about sampling.`

Better alternatives:

| Stale or risky Memory | Better approach                                        |
| --------------------- | ------------------------------------------------------ |
| Temporary task detail | Put it in the current chat or Workspace.               |
| Source fact           | Store source files in a Workspace and cite them.       |
| Broad behavior rule   | Rewrite as a specific Directive.                       |
| Project preference    | Keep only if it applies beyond the current source set. |

## Clean up Directives

<Steps>
  <Step title="Open Directives">
    Select the **Directives** tab.
  </Step>

  <Step title="Scan active rules">
    Look for rules that conflict with your current work.
  </Step>

  <Step title="Turn off uncertain rules">
    Disable a Directive before deleting it if you may need it again.
  </Step>

  <Step title="Edit broad rules">
    Rewrite broad Directives into specific behavior.
  </Step>
</Steps>

Overly broad:

```text theme={null}
Always be strict.
```

Better:

```text theme={null}
For quality review, flag unsupported claims, missing source evidence, unclear acceptance criteria, and conclusions that need SME confirmation.
```

## Use Analytics and usage signals

When available, use Memory analytics to spot:

* Memories that are retrieved often.
* Memories that are never used.
* Memories created automatically versus manually.
* Source patterns that may need review.
* Memory types that are overused.

High usage does not mean a Memory is correct. It means it may influence many responses, so review it carefully.

## Use Episodes and Knowledge Graph carefully

Episodes and Knowledge Graph views can help you understand how remembered context relates across interactions. Use them for review and cleanup, not as a replacement for source documents.

Ask yourself:

* Does this remembered concept still apply?
* Is this connection too broad?
* Does this belong in a Workspace instead?
* Could this bias future work?

## Prepare for a new project

Before starting a new major project:

<Steps>
  <Step title="Search old project terms">
    Remove stale Memory tied to old products, sites, vendors, or process assumptions.
  </Step>

  <Step title="Check Directives">
    Keep general review standards. Turn off project-specific rules.
  </Step>

  <Step title="Create useful preferences">
    Add stable preferences such as preferred table formats or review language.
  </Step>

  <Step title="Move sources to a Workspace">
    Put project files in a Workspace instead of Memory.
  </Step>
</Steps>

## Ask Sofie to audit personalization

You can ask Sofie to help review what may be influencing work:

```text theme={null}
Review my Memory and Directives for stale, overly broad, duplicated, or sensitive entries. Suggest which to keep, edit, disable, or delete. Do not delete anything without my confirmation.
```

For a specific workflow:

```text theme={null}
Review my Memory and Directives for deviation investigation work. Flag anything that could cause unsupported root-cause conclusions or source confusion.
```

## Related guides

* [Memory](/personalize/memory)
* [Directives](/personalize/directives)
* [Saved prompts](/prompts/saved-prompts)
* [Context windows and summarization](/chat/context-windows-and-summarization)