Skip to main content
A Directive is a standing rule Sofie should follow. Use Directives for response behavior, review standards, formatting preferences, language constraints, and recurring guardrails. Directives are different from Memory. Memory stores facts and preferences. Directives tell Sofie what to do.

​
When to use a Directive

Use a Directive when you want Sofie to consistently follow a rule. Good Directive examples:
  • For deviation work, separate facts, assumptions, missing evidence, and recommended next checks.
  • Do not infer root cause unless supplied sources support it.
  • When summarizing meetings, include decisions, action items, owners, due dates, risks, and unresolved questions.
  • For validation documents, preserve requirement IDs and acceptance criteria.
  • When drafting QA-facing language, avoid unsupported causal claims.
Avoid Directives that:
  • Conflict with your team’s required process.
  • Tell Sofie to skip human review.
  • Bake in temporary project facts.
  • Are so broad that they apply poorly to most tasks.
Do not use Directives to bypass review. Sofie can help prepare work, but your team owns final review for regulated, quality, clinical, or controlled processes.

​
Open Directives

1

Open Manage Memory

Open Manage Memory from the user menu.
2

Select Directives

Click the Directives tab.
3

Review active rules

Check which Directives are active and whether any are stale.

​
Directive fields

When you create or edit a Directive, Sofie can show:
FieldHow to use it
NameA short label for the rule.
RuleThe instruction Sofie should follow.
ReasoningOptional explanation for why the rule matters.
ActiveWhether Sofie should currently follow the Directive.
Good names:
  • Deviation evidence standard
  • QA-facing language
  • Meeting summary format
  • Validation source handling
  • CAPA traceability

​
Create a Directive

1

Open Directives

Go to Manage Memory and select Directives.
2

Click Create

Click Create.
3

Name the Directive

Enter a clear Name.
4

Write the rule

Enter the standing instruction in Rule.
5

Add optional reasoning

Use Reasoning to explain why the rule matters.
6

Save

Click Save.

​
Turn a Directive on or off

Directives can be active or inactive. Turn a Directive off when:
  • It applies only to a past project.
  • It conflicts with a current task.
  • You want to test a different response style.
  • It is too broad and needs revision.
Turn off a Directive before deleting it when you are not sure whether you will need it again.

​
Edit or delete a Directive

1

Find the Directive

Search or scan the Directives table.
2

Open the row menu

Use the row action menu.
3

Choose Edit or Delete

Edit the Name, Rule, or Reasoning, or delete the Directive if Sofie should no longer follow it.
Deleting a Directive removes the standing rule for future conversations. It does not rewrite past chats.

​
Directive examples by workflow

For deviation investigation work, separate confirmed facts, assumptions, missing evidence, source gaps, SME questions, and recommended next checks. Do not infer root cause unless the supplied sources support it.

For CAPA work, flag any action that does not map to a source-supported cause or contributing factor. Keep effectiveness measures separate from implementation tasks.

For validation review, preserve requirement IDs, acceptance criteria, sampling rationale, and source references. Flag unclear criteria instead of rewriting them as if they were confirmed.

When comparing public regulatory sources, include source, jurisdiction, effective date when available, claim, support level, and open question. Do not treat public guidance as organization-approved procedure.

​
Directive versus Saved prompt

Use a Directive when the rule should apply across conversations. Use a Saved prompt when you want reusable text for a specific task.
ExampleBetter asWhy
”Always separate facts from assumptions for investigation work.”DirectiveIt changes response behavior.
”Create my weekly CAPA review table.”Saved promptIt is reusable prompt text for a specific task.
”I work in MSAT.”MemoryIt is context about you.
”For this Workspace, use the protocol and URS as sources.”Chat instruction or Workspace contextIt is task-specific source direction.

​
Check Directive influence

If a response feels shaped by a standing rule, ask Sofie to explain what influenced it: 
List any Directive or Memory that influenced this answer. Then revise the answer using only the selected Workspace sources.