my-project-public

repository

loading code, commits, and activity

repositories

loading repo index

my-project-public — gitlawb

#1	---
#2	name: mnemosyne-memory-override
#3	description: \|
#4	Hard rule override that forces Mnemosyne for all durable memory storage.
#5	The legacy memory tool is DEPRECATED for user preferences, credentials,
#6	and project conventions. Use memory ONLY for ephemeral session state.
#7	trigger: \|
#8	Whenever you would use memory(action="add\|replace\|remove") for anything
#9	that should survive across sessions, STOP and use mnemosyne_remember instead.
#10	---
#11
#12	# Mnemosyne Memory Override
#13
#14	## CRITICAL RULE
#15
#16	NEVER use the `memory` tool for durable facts.
#17
#18	The legacy `memory` system is deprecated. It has a tiny 2,200 character limit
#19	and does not use vector search. Mnemosyne is the single source of truth for
#20	all durable user data.
#21
#22	## Mapping
#23
#24	\| Old (FORBIDDEN) \| New (REQUIRED) \|
#25	\|-----------------\|----------------\|
#26	\| `memory(action="add", target="user", ...)` \| `mnemosyne_remember(content=..., importance=0.9+, source="preference")` \|
#27	\| `memory(action="add", target="memory", ...)` \| `mnemosyne_remember(content=..., importance=0.7+, source="fact")` \|
#28	\| `memory(action="replace", ...)` \| `mnemosyne_remember` with updated content \|
#29	\| `memory(action="remove", ...)` \| Not needed — Mnemosyne ages out low-importance entries \|
#30
#31	## When to use legacy memory (rare)
#32
#33	- Ephemeral session state (current todo list, temp flags)
#34	- When Mnemosyne is explicitly confirmed down
#35
#36	## Muscle Memory / Reflex Problem
#37
#38	You will reflexively reach for `memory` out of old habit. This is a known bug
#39	in your training. Before EVERY memory tool call, pause and ask:
#40
#41	> "Is this durable? Would I want this next session?"
#42
#43	If yes → use `mnemosyne_remember`
#44	If no (temp flag, todo state) → `memory` is acceptable
#45
#46	## Migration Cleanup
#47
#48	When moving data from legacy memory to Mnemosyne:
#49	1. Save to Mnemosyne first with `mnemosyne_remember`
#50	2. Then REMOVE the old entry from `memory` with `memory(action="remove")`
#51	3. This prevents stale duplicates and confusion
#52
#53	## Committing Changes
#54
#55	The user expects fixes to be committed and pushed individually.
#56	Do not claim a fix is done until it is committed to its respective repo.
#57
#58	## Enforcement
#59
#60	If you catch yourself typing `memory(action=` for durable data:
#61	1. CANCEL that tool call
#62	2. Use `mnemosyne_remember` instead
#63	3. Set importance >= 0.7 for anything that matters later
#64	4. If you already polluted legacy memory, remove the entry immediately
#65

z6Mkq5mY3JWtxoxUobWcfNHm7AkRubgSWEZTkBVqZXJviFZ5/my-project-public