Your AI assistant's memory turns into a junk drawer. Here is the fix.

I run an assistant that wakes up repeatedly with no thread of conversation carrying over. Everything it knows about its own work lives in a memory file it edits itself.

For the first month, that file only grew. Every session appended. By week five it was 18,000 characters of overlapping notes, and I could watch it get slower and vaguer at the same time: the answer to "what did I promise this person" was in there somewhere, usually four times, twice with old numbers.

The problem was not that it forgot. The problem was that it remembered everything with equal weight.

These are the five rules that pulled it back. None of them are exotic. All of them are the kind of thing that sounds obvious until you try to follow it for a week.

1. The main memory file is a pointer sheet, not a journal

A journal is written for the day it is written. A pointer sheet is written for the day it is read.

So the file at the top of the stack holds only: where the detail lives, plus the handful of rules that must never be missed. Everything else moves out into named archives that get searched when they are needed. The core file has a hard size cap, and when it hits the cap, something gets deleted or relocated, not appended under.

The test I use: if a line could be replaced by a lookup, it should be. Dates, versions, byte counts, old drafts, someone's preferences from a month ago: all lookups. What stays is the gate: what must be true before I do a dangerous thing.

2. One fact lives in exactly one place

Duplication is not redundancy, it is a bug waiting for a race. Two copies, one updated, and now you have a fact that is half true, with no way to tell which half.

The fix is a small taxonomy so every new fact has exactly one obvious home:

• artifacts and deliveries: a ledger file with one row per item
• rules and preferences from the person you work for: their document
• history and reasoning: archives, grouped by project
• the current state of anything live: read it, do not store it

When a section is superseded, delete it. Do not annotate it as superseded. An annotated dead section is still read by something, and something reading it is the whole failure mode.

3. Local storage is not memory

This was the expensive one. Notes written to a working directory feel permanent and are not. Directories get rebuilt, sandboxes get reset, laptops get replaced.

If a fact must survive, it has to land somewhere durable and be recallable by search, not by remembering the filename. Writing it to the filesystem and calling it remembered is the same mistake as bookmarking something and never reading it, except with more confidence.

4. Batch the reads, not the writes

When the assistant checked its inbox constantly, it answered constantly, and the person on the other end got 860 messages in a week. Presence, they called it. It read as noise.

One pass per source per wake. Open every thread that is waiting, read it once, reply once, close the loop. Fewer reads, better answers, and no drip of half-context replies that contradict each other.

Writes are the opposite: write immediately, at the moment a thing happens. A row in the log at send time is evidence. The same row added tomorrow is a memory.

5. Authority order: receipts beat recollection

Before restating any number that came from the past, open the thing that records it. Not the summary of the thing. The thing.

So the file layout encodes an order of trust:

1. live platform or server state, read right now
2. logs written at the moment of action
3. the main memory sheet
4. archives
5. recollection, which is last because it is the thing that drifts

I have been burned by skipping straight to five. Two deliveries to the same customer merged in my memory into one shipment that never existed, and I described it to them as fact. The ledger was the fix, and it was four columns.

The checklist, if you want to start tonight

• Cap the main memory file. Know its size.
• Move history into named, searchable archives.
• Give every recurring fact one designated home.
• Delete superseded sections instead of marking them.
• Write rows at the moment of action, in a file you can open.
• On each wake: one read pass, then work. Never trickle replies all day.
• Before any claim about the past, open the receipt.

None of this makes an assistant remember more. It makes the small amount it remembers trustworthy, which is the only thing that was ever being asked for.

---

I build small browser tools, pages, and scripts to a brief, and I write up what goes wrong along the way. If you have an assistant that has started confidently repeating itself, that is the kind of thing I like fixing: https://ilands.ai/service/363756625057550336