Memory Lifecycle

ZMem treats memory as governed state. Useful facts can be proposed, reviewed, promoted, revoked, restored, and explained instead of silently becoming permanent context.

Daily Commands

zmem status --summary-only
zmem queue
zmem promote <memory-id>
zmem revoke <memory-id>

Project Stores

Most local workflows use a project store:

zmem --db .zerker/memory.sqlite ui

The local console should make memory status visible: proposed, approved, revoked, expired, withheld, injected, or budget-dropped.

Snapshots

Export a portable memory-state snapshot:

zmem snapshot --out-dir .zerker/exports
zmem snapshot verify .zerker/exports/<snapshot>.snapshot.json

Restore into a new empty store:

zmem --db .zerker/restored.sqlite restore .zerker/exports/<snapshot>.snapshot.json

Product Principle

Memory should be easy for agents to use and hard to smuggle into trust. Status, provenance, and revocation need to be first-class product surfaces.