Memory Rules

What goes into ../Memory/ versus Wiki/.

Wiki/

Stable knowledge about the project. Atomic notes, cross-linked. Updated when the underlying repo changes. Examples: Crawlee Scraper, Reklamspärr, Pipeline.

A wiki note answers: what is X and how does it work right now?

Memory/

Session-scoped or person-scoped state. Mirror of the Claude auto-memory at ~/.claude/projects/memory/. Examples:

• User preferences (“use Bun, never npm”)
• Past decisions and their reasoning
• Sticky reminders (“Bolagsverket Öppet API is IP-blocked, don’t suggest it again”)
• Pointer files (MEMORY.md is the index)

A memory note answers: what should the agent remember about this user/session that doesn’t belong in the project’s permanent docs?

Boundaries

Belongs in Wiki	Belongs in Memory
The 6 Crawlee extraction strategies	”User wants the Obsidian vault as the LLM wiki”
Migration runner contract	”User prefers rtk to plain Bash for token cost”
GDPR Article 14 obligation	”We discussed and rejected ABPI.se because of ToS”
Schema of companies table	”User asked us to skip dotenv, Bun handles it”

Sync direction

The Claude auto-memory path is canonical for memory. ../Memory/ mirrors it for human readability inside Obsidian. When the auto-memory changes substantively, copy the relevant feedback_*.md / project_*.md / user_*.md files into ../Memory/.

Do not edit ../Memory/ directly as a primary source — those edits will be overwritten by the next sync.

See also

Wiki Conventions, Lint Checklist, Index.