The user-level shared memory section raises a question the piece doesn't quite cover: what happens when two agents write conflicting facts about the same user close together in time, not months apart where decay scoring would naturally handle it. Say a support bot logs "Alice moved to MySQL" right as a sales bot is still reading the older "Alice uses PostgreSQL" fact for a recommendation it's about to make. Decay scoring solves staleness over time, but a same-day write race is a different problem -- is that resolved at the write layer (last-write-wins, versioning) or left to whoever calls the API to serialize their own writes?