Memory hygiene, the routine that keeps memory alive
Memory without care decays. The routine: 15 min weekly, 15 min monthly, 30 min quarterly.
Memory is not a cache, memory is a database
Treat memory like a kitchen. You can cook in a clean kitchen. You can also cook in a dirty kitchen, but everything takes longer, you lose track of where things are, and eventually the food tastes wrong.
Same with memory. The AI can work with messy memory. But context pollution kicks in, retrieval gets fuzzy, sycophancy compounds. Cleaning weekly costs less than cleaning never plus rebuilding from scratch nine months later.
This lesson gives you the routine. Three frequencies, clear tasks. Roughly 20 minutes per week total.
The weekly routine
Once a week. Pick a day, stick with it. We use Sunday evening because the week's learnings are still fresh.
Surface stale learnings. Most memory servers track when each learning was last used. Stale equals old plus rarely accessed. nex_proactive shows you the list. Per entry decide, keep, archive, correct.
Resolve contradictions. nex_contradictions(action: "list") shows conflict pairs. Read, decide which is current, invalidate the other.
Tag this week's additions. Look at entities and learnings created in the last seven days. Add project tags so memory does not bleed across contexts.
Verify the always-on switch. Open a fresh session. Don't say anything about memory. Ask a project-specific question. If the AI answers with concrete details, the always-on policy is working. If not, run nex_profile save.
Note one anti-pattern. Write down what the AI got wrong this week. Small. "Suggested lodash where I prefer vanilla." Save as a learning with category mistake. Compound effect over a year is enormous.
The monthly routine
Once a month. We do it on the 1st because that date is easy to remember.
Dedupe scan. nex_deduplicate(action: "scan", minSimilarity: 0.85) finds near-duplicates that crept in over time. Merge them.
Run confidence decay. nex_decay run. Reduces confidence on facts not retrieved in a while. FadeMem in StudioMeyer Memory, confidence rebalancing in Mem0. One command.
Synthesize learning clusters. When you have five or more learnings in the same category pointing at a pattern, generate a semantic summary. nex_synthesize(action: "scan") lists candidates. Generate per cluster if the effort is worth it. The synthesis has higher signal-to-noise than the individual learnings.
The quarterly routine
Every three months. Bigger cleanup.
Reset the knowledge profile. nex_profile(action: "save"). Your top-15 entity snapshot then reflects what matters NOW, not what mattered three months ago.
Privacy audit. Search for personal-tagged stuff in work context, work-tagged stuff in personal context. If leaks exist, fix or archive.
Prune by relevance. Entities with no activity in 90 days are usually dead weight. Walk through and archive.
Server re-eval. Every three months ask, is the memory server I picked still the right one? Did the project change? Did Mem0 or Zep get better? Recipe 4.8 is your re-eval grid.
Write a quarterly retro. Short note: how Q1 2026 went with memory, what worked, what did not. Save as a learning with tag retrospective. Future-you in a year benefits enormously.
How to make it habitual
The weekly routine is the only one that really has to be habitual. Monthly and quarterly are easy if the weekly is in place.
Calendar entry. Recurring event Sunday 8 PM. Title "Memory hygiene". Description with link to this lesson.
Self-policing. Tell the AI to remind you. Many memory servers support nex_delegate with due dates. The AI itself surfaces "you have not run hygiene in 8 days" on next session start.
Track a single metric. How many stale learnings did you archive this week. Or how many contradictions you resolved. Over a year you can see whether your routine keeps pace with growth.
When you skip a week or two
Nothing breaks. The system keeps running. Stale learnings just accumulate slightly more. If you skip three weeks, the weekly routine takes 25 minutes instead of 15 once you come back. Past a month, do the monthly routine plus skip the weekly catch-up, same effect, less guilt.
The point is rhythm, not perfectionism.
What this lesson does NOT solve
It does not solve sycophancy at the architectural level (lesson 08 has the background, the technical limit is real). It does not solve the cross-tool problem (lesson 05). It does not solve "I picked the wrong vendor", that is recipe 4.8 plus a migration plan.
What it solves: the slow, invisible degradation that is the real reason most memory deployments stop being useful after a few months.
Further reading
Recipe 4.10 (memory hygiene routine) has the full step-by-step walkthrough with all tools and commands. This lesson gave you the concept, the recipe gives you the hands-on instructions.
That completes Level 4 contentwise. Capstone in lesson 07, plus the two bonus lessons 08 (sycophancy) and 09 (hygiene). You now have the memory substrate plus the risks plus the maintenance. From here memory is no longer a topic, it is just the substrate.