Context
Mimir now has mimir memory list|show|explain|revoke, but public users need a clearer operator-facing surface for inspecting what exists, why it exists, and how it changed over time.
Scope
Design and implement an initial audit/reporting surface over governed memory records, revocation drafts, draft lifecycle events, and access/visibility metadata.
Acceptance Criteria
- Operators can inspect current records, revoked/tombstoned records, provenance, and supersession/revocation history.
- Output is usable as CLI text and has a path toward TUI or static HTML reporting.
- Delete semantics remain append-only revocation/tombstone, not physical mutation of canonical memory.
- Raw draft contents are not exposed accidentally through metadata-only status views.
Guardrails
Do not add any direct agent write path. All durable changes still go through the librarian boundary.
Context
Mimir now has
mimir memory list|show|explain|revoke, but public users need a clearer operator-facing surface for inspecting what exists, why it exists, and how it changed over time.Scope
Design and implement an initial audit/reporting surface over governed memory records, revocation drafts, draft lifecycle events, and access/visibility metadata.
Acceptance Criteria
Guardrails
Do not add any direct agent write path. All durable changes still go through the librarian boundary.