V2 was trying to make six residents feel coherent. They had routines, needs, relationships, facts, and allowed places. Every interaction added another event to the world’s active memory.
In the historical build described in the July 30 diary, old events never left. The visit grew longer, the record grew with it, and the browser eventually lagged.
The fix was a boundary
The current V2 build keeps ten recent events. Cooldowns stop the same event from firing too often. Suppression and loop guards prevent the world from talking itself into a circle. Reloading starts a fresh visit.
This turns history into a working memory. The island remembers enough to make the next action sensible without carrying every old interaction forever.
The useful lesson: a complete transcript is not the same thing as useful world state.
What is known about the slowdown
The dated builder account links unbounded event retention with worsening browser performance. It does not include a profiler trace, so no single measured bottleneck can be named.
The current WorldStore’s ten-event limit, cooldowns, suppression rules, and loop guards are present in current source. They correct the class of problem without proving the exact frame-time profile of the older build.
V2 still stores state only in memory. Reset builds a new WorldStore, and a page reload begins a new visit. Reload-safe persistence begins in V3.