Memory Hygiene Control Pack 20260731

Overview

This net-new draft implements the 2026-07-31 Merlin priority memory-hygiene-control-pack. Its stdlib-first analyzer converts redacted local evidence notes into a deterministic confidence report covering: memory owner, source citation, captured date, last verified, freshness window, contradiction review, duplicate review, retention rule, expiry rule, boundary review, repair proposal, restore plan, reviewer signoff.

It is advisory and read-only. It does not discover private data, call networks, control services, mutate files, install software, transact, or initiate billing activity. It does not certify a downstream release, security, listing, package, live, or production state.

When to Use

• Before acting on redacted local notes for memory-hygiene-control-pack.
• When a reproducible PASS, REVIEW, BLOCKED, or ERROR evidence-gap report is needed.
• To prepare clean, risky, missing, guarded-path, and oversized-input cases for independent Viper QA.

Do not use it to discover, rewrite, archive, or delete memory automatically; schedule work; deploy; publish; package; or create products.

Safety Contract

• Reads only direct --text or one explicitly supplied local notes file.
• Refuses hidden or sensitive-looking paths, symlinks, non-files, and inputs over 200,000 characters.
• Uses Python standard-library modules only and always reports mutated_files: [].
• Local PASS is advisory and is not independent approval or authorization to remediate.

Main Script

scripts/memory_hygiene_control_pack.py supports --notes, --text, --self-test, and --json.

Operator Workflow

1. Prepare redacted evidence notes. Complete when no secrets or private personal data are present.

2. Run python3 scripts/memory_hygiene_control_pack.py --notes notes.txt --json. Complete when structured output is returned and source content is unchanged.

3. Review every risk and missing signal. Complete when each finding has an owner or explicit deferral.

4. Hand unchanged artifacts and local evidence to Viper. Complete while status remains PENDING_VIPER.

Result Semantics

• PASS: at least nine expected signals and no risk signal.
• REVIEW: partial evidence or one bounded concern.
• BLOCKED: at least two risks or evidence score below 25.
• ERROR: missing, guarded, oversized, or unreadable input.

Test Scenarios

• All expected signals with no risks should produce PASS.
• Two or more explicit risk phrases should produce BLOCKED.
• Missing input should return ERROR with missing_notes.
• Hidden, sensitive-looking, symlinked, directory, and oversized inputs should be refused without mutation.

Common Pitfalls

1. Treating local analyzer PASS as independent approval.

2. Supplying secret values instead of redacted evidence references.

3. Mistaking recommendations for authorized remediation or execution.

4. Omitting ownership, restore, rollback, timestamp, or reviewer evidence.

Verification Checklist

• [ ] python3 -m py_compile scripts/memory_hygiene_control_pack.py exits 0 with isolated bytecode output.
• [ ] Two --self-test --json runs are byte-for-byte identical.
• [ ] Self-test returns ok=true, clean=PASS, risky=BLOCKED, and mutated_files=[].
• [ ] Input guards and repository security/static checks pass.
• [ ] Draft remains PENDING_VIPER.

Draft Status

PENDING_VIPER — Iceman build evidence is not an independent downstream verdict.