What Personal-Agent Memory Looks Like at Scale
This is Part 2 of Memory Is Not a Database . Part 1 develops the evidence-first memory model; this part asks what happens when memory, users, sources, tasks, and agents all grow—but not at the same rate. TL;DR: “Scale” is not one number. Memory volume, users, sources, concurrent tasks, agents per user, and agents per task stress different boundaries. Personal memory, task state, agent scratch space, the action journal, and procedural memory need different ownership and lifecycles. Partition by person, coordinate by task, and give each agent the smallest context and authority its role requires. Scale has multiple dimensions A personal-agent platform can grow along several largely independent axes: Dimension What grows Primary pressure Architectural response Memory per person Years of conversations, events, documents, actions, and derived beliefs Retrieval precision, consolidation, staleness, and storage tiers Keep a compact current model; incrementally summarize and consolidate; ...