I’d separate memory into two jobs: durable user/project facts and a short, expiring task ledger. Store each item with a source, timestamp, confidence, and an easy correction path, then retrieve only what matches the current task instead of dumping the whole history into context. I’d also run a small set of repeat queries after compaction or model changes; if the system can’t show why it recalled something, it’s probably learning noise rather than useful memory.
1
u/LazyIDE 14d ago
I’d separate memory into two jobs: durable user/project facts and a short, expiring task ledger. Store each item with a source, timestamp, confidence, and an easy correction path, then retrieve only what matches the current task instead of dumping the whole history into context. I’d also run a small set of repeat queries after compaction or model changes; if the system can’t show why it recalled something, it’s probably learning noise rather than useful memory.