Memory needs an operating budget.

Video caption

Memory needs an operating budget.

False holds consume people; false greens consume recovery.

Events invalidate; protected lookup confirms.

My rule: Removal and correction are routine operations.

#EricFieldNotes

Full written post / accessibility read

Companies budget for adding agent memory and forget the work of revoking it. Customer exceptions, policies and architecture decisions change. Without update triggers and expiry, yesterday's rule can feel official tomorrow.

For each memory class, name its source, change owner, revalidation interval and escalation. Track stale packets, missed updates, reviewer minutes and time to accepted resolution. Saved-note count is not an outcome metric.

A policy owner publishes a new version. The steward records supersession. At a consequential action, the host checks the source again because notifications can be delayed or dropped.

Do that because a larger memory can increase confident staleness. Treat update latency and false intervention cost as service measures, and retire memory classes whose owners cannot keep them current.

#EricFieldNotes

Four-beat scene transcript

1. Memory needs an operating budget.

Companies budget for adding agent memory and forget the work of revoking it. Customer exceptions, policies and architecture decisions change. Without update triggers and expiry, yesterday's rule can feel official tomorrow.

Visual: A stored note without an owner becomes debt.

2. Measure stale interventions.

For each memory class, name its source, change owner, revalidation interval and escalation. Track stale packets, missed updates, reviewer minutes and time to accepted resolution. Saved-note count is not an outcome metric.

Visual: False holds consume people; false greens consume recovery.

3. Write a source-change contract.

A policy owner publishes a new version. The steward records supersession. At a consequential action, the host checks the source again because notifications can be delayed or dropped.

Visual: Events invalidate; protected lookup confirms.

4. Fund invalidation first.

Do that because a larger memory can increase confident staleness. Treat update latency and false intervention cost as service measures, and retire memory classes whose owners cannot keep them current.

Visual: Removal and correction are routine operations.

Research and claim limits

• LongMemEval, ICLR 2025 (S206)
• OpenAI Agents SDK handoffs (S207)

The examples identified as illustrative or simulated are design probes, not reported incidents. Vendor specifications do not establish workload performance.