Great point — and agreed OpenClaw has real memory primitives. Digital Citadel is not a replacement for OpenClaw memory. It's an operations layer on top of it for continuity failures we kept seeing in the wild (session pointer drift, recovery protocol drift, restart races, missing required-read sentinels, etc). So the stack I'm using is: 1) native OpenClaw memory/search 2) disciplined file state (daily log + active tasks) 3) recovery protocol hardening for compaction vs true session rollover In our case, the painful incidents were mostly infra/protocol issues, not model IQ or missing built-ins. Would love to compare notes on your /new recovery patterns too 🤝