Skip to main content
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.
Availability can vary by organization and feature settings.

​
Clean up Memory

1

Open Memories

Open Manage Memory and stay on the Memories tab.
2

Search by project or topic

Search for product names, project names, departments, sites, or recurring workflow terms.
3

Check content

Confirm each Memory is stable, useful, and appropriate for future conversations.
4

Check type and importance

Make sure Type and Importance match how much the Memory should influence Sofie.
5

Edit or delete

Edit vague Memory. Delete stale, duplicated, temporary, or sensitive Memory.
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:

​
Clean up Directives

1

Open Directives

Select the Directives tab.
2

Scan active rules

Look for rules that conflict with your current work.
3

Turn off uncertain rules

Disable a Directive before deleting it if you may need it again.
4

Edit broad rules

Rewrite broad Directives into specific behavior.
Overly broad:
Better:

​
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:
1

Search old project terms

Remove stale Memory tied to old products, sites, vendors, or process assumptions.
2

Check Directives

Keep general review standards. Turn off project-specific rules.
3

Create useful preferences

Add stable preferences such as preferred table formats or review language.
4

Move sources to a Workspace

Put project files in a Workspace instead of Memory.

​
Ask Sofie to audit personalization

You can ask Sofie to help review what may be influencing work:
For a specific workflow: