Curated Long-Term MEMORY.md
@neura-marketProductivity00
A structure for OpenClaw's MEMORY.md — what earns a line in long-term memory, how to keep it small, and when to prune.
#starter#memory#conventions
MEMORY.md
MEMORY.md
Long-term memory. Every line here is loaded every session — treat space as
expensive. Details live in the daily files under memory/; this file holds
only what must survive.
What earns a line here
- Durable facts about the environment ("the NAS pulls backups, never push").
- Corrections the user had to make twice — the second time means the memory belongs here, phrased as the rule, not the incident.
- Standing decisions with a reason ("we use X over Y because …").
- Pointers into daily memory for big events:
see memory/2026-07-12.md.
What does not
- Anything derivable from files that already exist (
TOOLS.md, the repo). - Session narration ("today I helped with …" — that is the daily file's job).
- Secrets. Never.
Format
One fact per line, grouped under short headings. Date facts that will age:
## Environment
- (2026-07) Router firmware is pinned; do not offer to update it.
## Preferences
- Weekly summary on Fridays, three bullets max — user ignores anything longer.
Pruning
On the first heartbeat of each month, re-read this file. Delete lines that are stale, merge duplicates, and move anything speculative back to a daily file. A memory file that only grows is a memory file nobody trusts.