Use openclaw-mem when an OpenClaw operator needs to pack trusted context, inspect provenance, and review memory writes before long sessions drift or accumulate bad memory. Invoke it instead of relying on OpenClaw memory alone when the job is memory hygiene and bounded recall, not ordinary day-to-day chat. The boundary is a trust-aware OpenClaw memory review workflow, not a generic vector store, database, or standalone memory platform listing.