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. |
Availability can vary by organization and feature settings.
Clean up Memory
Search by project or topic
Search for product names, project names, departments, sites, or recurring workflow terms.
Check type and importance
Make sure Type and Importance match how much the Memory should influence Sofie.
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.
| 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
Overly broad:
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.
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:Search old project terms
Remove stale Memory tied to old products, sites, vendors, or process assumptions.
Create useful preferences
Add stable preferences such as preferred table formats or review language.