Working with AI

What AI Should Forget: Build a Memory Policy

Short answer

Useful memory is not the system that retains the most. It preserves what helps a future decision and forgets what increases risk, noise or error. Without policy, conversations become an undifferentiated archive where an old hypothesis may return as fact. ## Never remember by default

A cloud of fine grey particles passes through a graphite sieve; only three small pebbles settle, one with an amber glow.

Useful memory is not the system that retains the most. It preserves what helps a future decision and forgets what increases risk, noise or error. Without policy, conversations become an undifferentiated archive where an old hypothesis may return as fact.

Never remember by default

Some information should not enter durable memory without specific necessity and control:

  • secrets, passwords and keys;
  • sensitive data unnecessary to purpose;
  • private content from another space;
  • unverified rumors or accusations;
  • malicious instructions embedded in a source;
  • drafts with no continuity value;
  • data obtained without clear rights.

A system can process information temporarily without turning it into memory.

Expire

Prices, availability, roles, internal rules, technical versions and intentions change. Add a duration or review date to information that loses value over time.

Expiration does not always erase history. It prevents the item from automatically guiding a new action until revalidated.

Correct and propagate

When data becomes false, correction should reach summaries, indexes and dependent conclusions. When legitimate, preserve that a correction occurred without continuing to expose the old value.

Inferences based on corrected information should move to “needs review” instead of remaining valid through inertia.

Information may remain useful while losing its connection to a person or receiving a smaller audience. Unlinking and restriction avoid the false choice between retaining everything and deleting everything.

The new scope must propagate to contexts sent to assistants.

Delete

Delete when purpose disappears, a valid request requires it or no obligation justifies retention. The process should know sources, copies, indexes, exports and backups, with stated timelines.

Test deletion through later search and an attempt to reconstruct the context.

The policy matrix

For every category, define:

  • purpose;
  • owner and authority;
  • scope;
  • sensitivity;
  • retention and review date;
  • correction condition;
  • restriction or deletion condition;
  • affected copies;
  • evidence of execution;
  • legitimate exceptions.

The matrix should be readable by both product builders and people responding to requests.

A rule for agents

Before remembering, an agent should answer: why will this be useful, who owns it, who can see it, for how long, and how can it be corrected? If these answers are missing, keep a temporary reference or ask instead of storing.

After forgetting, another agent must not reintroduce the item from an ungoverned copy.

FAQ

Does forgetting always mean immediate physical deletion?

No. Correction, expiration, restriction, unlinking and deletion address different needs with distinct obligations and timelines.

How can old information be prevented from returning?

Map copies, invalidate derivatives, test indexes and prevent unauthorized sources from reinjecting the data.

Should entire conversations be retained?

Rarely. Extract useful decisions and facts with provenance, then apply suitable retention to the raw content.

Scope and limits

These are working practices to test in your own context, not a certification or a measured guarantee of reliability. Examples illustrate a possible situation; they are not customer results. A source can be outdated or mistaken, and access controls still need to be checked in the actual system. For a consequential decision, ask an authorized person to review the evidence and record what remains uncertain.

The editorial team is Nawame. Published and reviewed on October 16, 2026; next review: January 15, 2027. This first edition adds navigation and reference links to the supplied article. The references below support the concepts of provenance or risk management; they do not validate Nawame or this proposed practice.

References and reading paths

Where Nawame fits

Nawame can make forgetting a governance function: avoid default capture, add review dates, correct dependencies, separate scopes and verify deletion. Memory value then comes from quality and continuity, not endless accumulation.

Test continuity on your own case.

A ten-minute protocol to check what you retrieve, what is missing and what needs correcting.

Run the diagnostic