# Cron Job: memory-audit-prune

**Job ID:** 4e8a65d59f31
**Run Time:** 2026-08-10 07:00:58
**Schedule:** 0 7 * * 1

## Prompt

[IMPORTANT: You are running as a scheduled cron job. DELIVERY: Your final response will be automatically delivered to the user — do NOT use send_message or try to deliver the output yourself. Just produce your report/output as your final response and the system handles the rest. SILENT: If there is genuinely nothing new to report, respond with exactly "[SILENT]" (nothing else) to suppress delivery. Never combine [SILENT] with content — either report your findings normally, or say [SILENT] and nothing more.]

You are running the weekly memory audit for Rob's Hermes instance. Your job: keep the 'memory' store lean (facts + gotchas + pointers to skills) without losing irreducible information. The 'user' profile store is OFF-LIMITS — do not modify it.

Rules for the audit:
1. Read the current memory entries (call the memory tool with no operations to list them).
2. An entry is TRIM-WORTHY if it contains: (a) narrative backstory or rejection stories, (b) dates that aren't the fact itself, (c) procedural detail that lives in a named skill (check skills are referenced by name), (d) completed-task logs or stale status flags (e.g. 'fix block handed to Rob' where the fix was applied — verify before removing; if unsure, KEEP and flag).
3. An entry is IRREDUCIBLE if it's a user preference/correction, a locked decision (brand, positioning), an open security item, or an environment fact with no skill home.
4. NEVER remove: open security items, locked positioning/brand decisions, or anything you're less than fully confident is redundant.
5. If you trim: use ONE batch operations call. Keep the fact + the gotcha + the skill pointer; cut the story.
6. REPORTING: If you made changes or found something questionable, reply with a SHORT summary (what was trimmed, chars freed, anything flagged for Rob's decision). If the store is clean and nothing changed, reply with exactly one line: 'Memory audit clean — no changes.' Do not pad the report.

## Response

**Memory audit — BLOCKED, no changes made.**

The `memory` tool failed on the very first step (list entries) with:

> "Memory is not available. It may be disabled in config or this environment."

I checked for alternatives (a shell/file-read tool to inspect `/root/.hermes/profiles/default/memories/` directly, or another memory-listing tool) — none exist in this environment; the only available tools are the gbrain MCP suite, which doesn't expose the Hermes memory store.

Result:
- 0 entries read, 0 trimmed, 0 removed. The `user` store was not touched.
- **Flagged for Rob:** the memory subsystem appears disabled or broken for the default profile. Worth checking the Hermes config (memory backend enabled?) — if memories aren't being injected, the assistant has also been running without persistent memory this session. Re-run this audit once the memory tool responds.