Documentation navigation
Docs/Concepts/When to use it

When to use it

Decide which information is worth saving and which short-lived notes can stay out of memory.

Use Lore when the information will matter again.

Decision guide

SituationStore it?Better shape
A user preference should affect future repliesyespreferences://user/... or a focused preference node
A project has a repeatable command or deployment ruleyesproject://project_name/workflow
An agent-specific hook or runtime behavior mattersyescore://agent/<channel>
A one-off error happened and is already fixedmaybestore only the durable lesson, not the whole log
You are brainstorming and may change directionnot yetwait until a decision stabilizes

When in doubt, ask two questions:

  1. Would forgetting this cause repeated work or mistakes?
  2. Can I describe the future situation where this memory should appear?

If the answer to both is yes, write a memory with a clear disclosure trigger.

What Lore is forLearn which facts, preferences, decisions, and rules should become durable memory.How Lore worksUnderstand the loop: boot context, recall, reading memories, writing durable changes, and review.Memory modelLearn the core memory shape: paths, domains, priority, disclosure, glossary terms, and generated views.Memory pathsUse stable memory paths and domains to keep memory easy to browse, link, and move.