Skip to main content
Memory stores durable facts and preferences Sofie may use later. Use Memory for information that should influence future conversations, such as your role, recurring work preferences, current project context, or the way you prefer review outputs. Memory is not a source of record. Use Workspaces, CoDrafts, CoSheets, CoMeetings, and cited sources for project evidence and controlled content.
Do not store sensitive or temporary details as Memory unless they should influence future Sofie conversations. Delete stale memories when your work changes.

​
Open Memories

Open Manage Memory from the user menu when available. The Memories page includes:
  • Memories
  • Directives
  • Episodes
  • Knowledge Graph
  • Analytics
This page focuses on Memories. For standing rules, see Directives.

​
What belongs in Memory

Good Memory examples:
  • I work in MSAT and prefer technical summaries with assumptions separated.
  • For validation reviews, I prefer tables with requirement ID, gap, rationale, and SME question.
  • My current project is a sterile fill-finish tech transfer.
  • When reviewing deviation materials, I prefer facts, assumptions, missing evidence, and next checks separated.
Avoid memories that are:
  • Too broad: Always be detailed.
  • Temporary: Today I am reviewing File A.
  • Source facts that belong in a Workspace or document.
  • Controlled conclusions that need source review.
  • Instructions better handled as Directives.

​
Memory fields

When you create or edit Memory, Sofie can show fields such as:
FieldHow to use it
ContentThe fact or preference Sofie should remember.
TypeClassify the Memory as Preference, Fact, Context, or Observation.
ImportanceUse High, Medium, or Low to indicate how important the Memory is.
ReasoningExplain why the Memory matters.
TagsAdd short labels that make Memory easier to review.
EntitiesAdd related names, systems, projects, or topics when useful.
ScopeReview whether the Memory is global or tied to a Workspace.
UsageSee how often the Memory has been used when available.
Write Memory as a stable sentence. Short, specific Memory is easier to review than a long paragraph.

​
Create Memory manually

1

Open Manage Memory

Open the Memories page from the user menu.
2

Stay on Memories

Select the Memories tab.
3

Click Create

Click Create.
4

Enter the content

Write the fact or preference in Content.
5

Set type and importance

Choose the Memory Type and Importance.
6

Add optional details

Add Reasoning, Tags, or Entities when they make later review easier.
7

Save

Click Save.

​
Review existing Memory

Use the Memory table to review:
  • Content: what Sofie may remember.
  • Type: preference, fact, context, or observation.
  • Importance: how strongly the Memory should matter.
  • Source: where the Memory came from when available.
  • Usage: how often it has been used.
  • Scope: whether it is global or Workspace-specific.
  • Created: when it was created.
Search Memory before creating a new one. This avoids duplicates and helps you find stale entries.

​
Edit or delete Memory

1

Search or scan

Find the Memory you want to change.
2

Open the row menu

Use the row action menu.
3

Edit or delete

Choose Edit to update the Memory or Delete to remove it.
4

Confirm deletion

Confirm only when Sofie should no longer use that information.
Delete Memory when:
  • Your role or project changed.
  • The Memory is too broad.
  • It contains temporary source facts.
  • It duplicates a clearer Memory.
  • It could bias future work in the wrong direction.

​
Memory and Workspaces

Use Memory for stable user preferences. Use a Workspace for source material and shared project knowledge.
InformationPut it in
”I prefer gap tables for validation reviews.”Memory
Project files, requirements, protocols, batch records, meeting notesWorkspace
”For this project, Product A is in Stage 2 PPQ.”Workspace source or project CoDraft
”When drafting for QA, keep conclusions source-backed.”Directive

​
Ask Sofie to use or ignore Memory

You can tell Sofie how to treat Memory in a chat. Use Memory: 
Use my usual validation review preferences, but cite source documents for each finding.
Ignore Memory: 
For this answer, do not rely on Memory. Use only the attached protocol and the selected Workspace.
Check Memory influence: 
Before answering, list any Memory or Directive that may influence your response.