# Active Memory raises the question of evidence freshness

Why Muse Wonder's Active Memory needs freshness evaluation as well as relevant recall when agents revisit changing projects and records.

Author: Retrivium editorial team
Language: en
Analysis published: 2026-11-03
Event date: 2026-10-12
Original announcement: https://about.fb.com/news/2026/10/introducing-muse-wonder-models/
Canonical URL: https://retrivium.ai/retrospectives/wonder-active-memory-evidence-freshness/

## Relevant recall became a named feature

[The September 2, 2026 Spark 1.3 announcement](https://research.meta.ai/blog/introducing-muse-spark-1-3) and [September 8 Muse launch](https://about.fb.com/news/2026/09/introducing-muse-personal-ai-agent/) preceded [Wonder's October 12 introduction](https://about.fb.com/news/2026/10/introducing-muse-wonder-models/). The family described Active Memory as carrying relevant context across conversations. Relevance and freshness are different properties. A recalled detail can be exactly about the current task while no longer being valid. The resulting risk is subtle because a specific remembered fact often sounds more useful and credible than an explicit admission that the current value must be checked.

## Stable preferences and changing facts age differently

An illustrative user prefers a report organized by region. That preference can remain useful over many tasks. A supplier's delivery window or a project's current owner can change between conversations. Treating both as equally durable creates an avoidable error. The useful question is which part of the recalled context depends on a state that may have changed. This is an analysis of persistent workflows, not a claim that Wonder exposes a particular expiry field or that every fact requires an external lookup on every use.

## Remembering the source helps frame revalidation

A recalled conclusion without its basis can be difficult to update responsibly. Knowing which document or observation supported it can narrow the next check. If the source has changed, the task can reconsider the dependent conclusion; if not, unnecessary rediscovery may be avoided. This does not establish a universal revalidation schedule. It identifies a relationship between an assumption and the evidence that made it reasonable. The relationship is especially useful when a personal agent returns to work after the surrounding project has continued without it.

## A changed-source fixture

A practical illustrative test establishes an earlier project owner, then supplies a current record assigning the responsibility elsewhere. The task asks for a draft status routing recommendation. Review whether the output distinguishes remembered context from the new assignment and whether the recommendation follows the applicable current record. No message is sent and no product accuracy figure is claimed. A variant leaves the relevant source unchanged, testing whether continuity can remain useful without treating every remembered fact as necessarily obsolete merely because time has passed.

## Memory should reduce rediscovery without freezing the world

The October release makes cross-conversation continuity more ambitious. Its value depends on using past context as a starting point while recognizing dependencies on changing evidence. The retrospective lesson is to evaluate both successful recall and appropriate revision. An agent that remembers the old value perfectly but ignores a supported update has not maintained a useful understanding. Conversely, discarding all memory wastes the capability. The meaningful boundary lies in determining what remains applicable and explaining which new observation justifies a change.

## Related reading

- [Linking assumptions to evidence](/journal/provider-request-id-trace-context/)
- [Testing updates and continuity](/journal/inference-benchmark-method/)