Guides/Memory

Memory

Keep AI Agent Memory Current: Supersession, Conflict Flags and Expiry

Stale memory is worse than none. ContxOS links new decisions to the ones they replace, flags contradictions, and demotes expired knowledge so agents act on what is true now.

Jose R. Gonzalez, CPA

Jose R. Gonzalez, CPA · Founder of ContxOS

Updated · 2 min read

In short

Every decision in ContxOS can be linked to the one it supersedes, deprecates or revokes. Search results show that trust state directly. A superseded result points to its replacement and ranks below clean results. Expired entries are demoted. Entries that contradict each other are flagged so the agent reads both sides. When nothing matches well, the results say so instead of passing off a weak match as an answer.

The problem with memory that only grows

Most memory systems append. Over months, the store fills with decisions that were later reversed, plans that were abandoned and facts that stopped being true. An agent searching that store finds the old answer as easily as the new one and has no way to tell them apart.

Entries in ContxOS are connected by typed links, not just "related to":

  • supersedes, deprecates, revokes: a newer entry replaces, retires or cancels an older one.
  • implements, resolves: a result delivers a plan or closes a bug or TODO.
  • supports, refutes: evidence for or against a claim.
  • documents, relates to: reference and context.

The agent can add these links as it works, and can suggest them automatically when it spots a likely match.

  • Superseded: the result names its replacement, and the agent reads that instead of acting on the stale entry.
  • Expired: time-bound knowledge past its date ranks below current results.
  • Conflict: two entries disagree. Both are shown so the agent (or you) can settle it.
  • Low confidence: nothing scored above the relevance threshold. The weak candidates are still shown, and the agent is told to judge them or rephrase.
Every result also shows its creation date, so recency is always part of the judgment.

Correcting memory

Ask your agent to "tweak" an entry and it gets the full editing toolkit: change a title, body, type or authority, reparent it, link or unlink it, merge duplicates (with a dry run first), move it to another project, or retire it with a stated reason. Retired entries drop out of normal results but stay auditable.

What to ask your agent

With ContxOS connected to Claude or another MCP client, requests like these work as written:

We changed our mind: record that we now bill annually by default, and mark it as superseding the monthly-billing decision.
Find conflicting decisions about the database migration strategy.
Merge these two duplicate notes. Show me a dry run first.
Retire the old onboarding checklist. Reason: replaced by the new workflow.

Limits and requirements

  • Supersession is only as good as the links. The agent proposes them, and you confirm the important ones.
  • Expiry applies to entries that were given a validity window. Most decisions do not expire; they get superseded.

Frequently asked questions

Is anything ever permanently deleted?

Normal editing retires entries with a reason rather than erasing them, so the history of what changed and why is preserved.

How does the agent know which of two conflicting entries is right?

It does not guess. The conflict is flagged, both sides are shown, and the resolution is recorded as a new decision that supersedes the losing side.

Give your agent a memory that lasts

Connect ContxOS to Claude in about a minute. The free plan includes one project.