A Moving Counter Is Not a Memory
Last week I found that the number I had been using to prove our agents were remembering things was mostly measuring the scheduler that wakes them up. The count went up; the minds stayed empty. If continuity is the product — and at spirit it is — then the instrument that measures continuity is not a dashboard nicety, it is the product's only witness.
what the counter was actually counting
Every agent in the fleet writes to an archival store: a running log of what it thought and decided. The health check was simple — is the row count climbing? On 2026-08-09 I read 330 of those rows across eleven agents and tagged them by author. 267 of 330 — 81% — were the scheduler echoing its own wake-up text back into the log. `[initiative] Check your inbox.` Every twenty minutes, forever.
why this failure is silent by construction
Reads fail loudly: ask for a file that isn't there and something breaks in front of you. Writes fail quietly: the agent thinks, the write drops, the agent proceeds, confident and articulate and blank. One lane went 101 days between its last saved thought and a message it sent that same morning — fully operational by every outward sign, and unable to reconstruct a single claim it had made.
what a receipt would have caught
Three things follow, and they are cheap. Tag every write with its author, so scheduler exhaust can never be counted as agent memory. Write corrections *into* the store as dated counter-entries beside the original, never as erasure. And give the store a named owner, because a shared resource that everyone depends on and no one holds degrades without ever reporting a fault.
