This breaks down why OpenClaw starts feeling more “human” over time: it’s not getting smarter so much as writing memories, rules, and session history back to disk and reloading them next turn.
Writing “memories” back to disk is cute until you hit reliability stuff: what’s their story for corruption and rollback when a write gets interrupted mid-session?
Interrupted writes are exactly why most apps don’t edit in place — you write a new file, fsync, then do an atomic rename (or keep memories. json + memories. json. bak).
