Tip2026-04-18#verification

Treat memory as evidence with an expiration date

Good memory is scoped. It records what the user decided, what a repo convention is, and which risks were already found. Bad memory stores private residue, stale status, or facts that should be rechecked.

Every memory-derived claim should answer two questions: when was this learned, and how likely is it to have changed? If the answer is 'recently unstable,' verify before acting.

The aha is that memory is not context magic. It is a cache, and caches need invalidation rules.

Aha moment

Agent memory is a cache. Useful caches have scope, freshness, and invalidation rules.

Try this

Store stable decisions and preferences, but re-check drift-prone facts before acting on them.

Watch for

  • Old status presented as current proof
  • Private residue stored when only workflow shape was needed
  • Memory outranking live repo, source, or user evidence