Memory Hygiene Manager 20260719

Overview

This draft converts local operator notes into a deterministic PASS / REVIEW / BLOCKED report for the 2026-07-19 Merlin priority. The stdlib-only analyzer checks memory source, capture date, review status, owner assignment, retention policy, expiry record, conflict detection, supersession, sensitive boundaries, audit trail, human approval, and cleanup evidence.

It is advisory and read-only. It does not mutate memory files, delete records, publish, package, deploy, create products, change billing, edit OpenClaw configuration, change cron state, or assert downstream release, security, live, or package status.

Merlin Source

• Brief: memory/merlin-build-brief.md dated 2026-07-19.
• Draft target: skills/memory-hygiene-manager-20260719/ for independent Viper testing.

Safety Contract

• Reads only direct --text or one explicitly supplied local notes file.
• Refuses hidden or sensitive-looking paths, symlinked inputs, non-files, and inputs above 200,000 characters.
• Uses Python standard-library modules only.
• Makes no network, subprocess, shell, package-manager, configuration, cron, deployment, publishing, billing, product, or credential-output calls.
• Every successful report includes mutated_files: [].

Main Script

• scripts/memory_hygiene_manager.py
• Modes: --notes PATH, --text TEXT, --self-test, and --json.

Result Semantics

• PASS: at least eight expected evidence signals and no risk signal; advisory only.
• REVIEW: partial evidence or one bounded concern needs operator review.
• BLOCKED: multiple risk signals or insufficient evidence; no live action should follow.
• ERROR: missing, sensitive, hidden, symlinked, oversized, or unreadable input.

Viper Scenario Seeds

• Complete memory hygiene notes should produce PASS.
• Notes containing all risk terms should produce BLOCKED.
• No notes should produce error=missing_notes.
• A symlink fixture should produce error=symlink_input_refused.
• A 200,001-character fixture should produce error=input_too_large.

Draft Status

PENDING_VIPER — Iceman local gates are not downstream QA, security clearance, release approval, packaging, deployment, or production verification.