Memory Health

ZMem can inspect the persisted state of a memory store without promoting, revoking, rewriting, or deleting any memory.

Run The Audit

Use the default local store:

zmem audit health --summary-only

Inspect a specific project store:

zmem --db .zerker/memory.sqlite audit health

JSON is the default machine contract. --summary-only prints a compact terminal view for an operator or agent.

What It Reports

The stable zerker.memory_health_report.v1 result groups observable findings into:

• stale or expired active memory,
• active lexical claims with conflicting values,
• exact duplicate content in the same type and scope,
• missing or incomplete write provenance,
• active memory with explicit high-risk evidence.

Each finding includes memory ids, a deterministic reason, and bounded evidence. Findings are sorted for reproducible output.

What It Does Not Prove

The audit does not decide whether a memory is factually or semantically true. It inspects persisted metadata, lineage, receipts, and deterministic lexical signals.

The audit never repairs findings. Use the separate maintenance preview to see whether any objective expiry boundary is eligible for an explicit transition:

zmem maintain preview --summary-only

Only reached expires_at boundaries are executable in the first maintenance contract. Every semantic or provenance-sensitive finding remains review-only. See Memory Maintenance for the preview, apply, and verify flow.

This separation keeps health inspection permanently read-only and makes later lifecycle changes explicit and receipted.