memory-quality-auditor

name	memory-quality-auditor
description	Audit memory retrieval quality (drift, staleness, citation-groundedness) and produce remediation backlog.
version	1.1.0
model	sonnet
invoked_by	both
user_invocable	true
tools	["Read","Write","Edit","Glob","Grep","Bash","Skill","MemoryRecord"]
args	--mode summary|full [--hours 24]
error_handling	graceful
streaming	supported
verified	true
lastVerifiedAt	"2026-02-22T00:00:00.000Z"
source	builtin
trust_score	100
provenance_sha	bf2941d04dc253b4

Memory Quality Auditor

Audit the memory system as a unified retrieval layer (STM/MTM/LTM files + index + spawn citation outcomes).

Scope

• Retrieval drift signals
• stale memory ratio
• evidence injection coverage
• citation usage/groundedness continuity

Workflow

1. Read memory artifacts and latest eval reports.
2. Compute quality metrics and threshold status.
3. Emit remediation backlog with TDD checks.
4. Record findings in memory and optional evolution recommendation.

Iron Laws

1. ALWAYS establish a baseline metric snapshot before auditing — drift is only meaningful relative to a prior measurement; auditing without a baseline produces absolute numbers that cannot identify regression.
2. NEVER close a memory finding without re-running the affected retrieval query — closing without verification creates false improvement metrics and masks persistent degradation.
3. ALWAYS include citation-groundedness checks in every audit run — uncited memory injections are the primary source of hallucination in agent spawns; skipping this check leaves the highest-risk failure mode undetected.
4. NEVER audit only the STM tier — degradation often originates in MTM/LTM promotion corruption; all three tiers must be sampled in every full audit cycle.
5. ALWAYS emit TDD-ready remediation items with a failing-test condition and expected metric threshold — vague findings ("memory quality is low") cannot be actioned by any agent.

Anti-Patterns

Anti-Pattern	Why It Fails	Correct Approach
Auditing without a baseline	Cannot distinguish regression from steady-state; all findings are ambiguous	Snapshot current metrics at session start; compute delta against the previous run
Closing findings without re-check	Produces false-positive resolution; degradation persists silently behind green metrics	Re-run the specific retrieval query after each remediation; close only on confirmed green metric
Skipping citation groundedness	Citation failures are the leading cause of agent hallucination; missing this check omits the highest-severity defect class	Include citation_coverage and grounded_ratio metrics in every audit report
Full-mode audit on every spawn