Anthropic shipping "dreams" is the industry admitting memory storage isn't the hard problem - maintenance is

When Anthropic announced Dreams for Managed Agents last week, the most interesting part wasn't the feature. It was the admission buried in the framing: agents that accumulate memory across sessions gradually make that memory *worse*, not better. Duplicates, contradictions, stale preferences, one-off context that got written down and never corrected. The more sessions run, the less the memory state can be trusted. That's not a retrieval problem. Better embeddings don't fix it. The issue is that no one is maintaining the record — deciding what changed, what conflicts, what should be carried forward, and what should be discarded. Anthropic's answer is a background "dream" pass that reads past sessions and produces a cleaned memory store. The research thread behind this goes back further — Generative Agents (2023) used reflection to synthesize higher-level memories, MemGPT framed it as an OS-style tiered memory problem. But Anthropic productizing it feels like the moment the industry officially acknowledges this as a primitive, not an edge case. Curious how others are handling this in practice: * Are you running any kind of memory hygiene loop in your agents? * Do you treat session transcripts and durable memory as the same thing, or keep them separate? * Has memory quality actually degraded for you in production over time, or is this more of a theoretical concern at current usage levels?