Mike Swanson
2a1ccfac73
memory-dream: read-only memory lint/consolidation analyzer (index, backlinks, stale refs, dup clusters, profile drift); additive-only --apply-safe, all merges/deletes are proposals. sync-memory.sh: additive repo<->harness-profile union (no delete/overwrite, conflicts surfaced), wired to a SessionStart hook. Migrates the useful profile-only memories into the synced repo store. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1.5 KiB
1.5 KiB
name, description, metadata
| name | description | metadata | ||
|---|---|---|---|---|
| project_memory_consolidation_automation | Goal - automate the memory lint/consolidation (/memory-dream) once the additive proposals prove trustworthy; phased rollout |
|
Mike wants the memory consolidation/lint process automated eventually (stated 2026-06-01). Phased so we never auto-wipe useful data:
- Now:
/memory-dreamruns report-only by default;--apply-safedoes additive-only fixes (append missing index lines, migrate profile-only memories in). Merges/dedups/deletions are PROPOSED only, human-approved. Build trust in the proposals first. - Next - automate the read-only half: the lint pass + additive
--apply-safeare non-destructive, so safe to run unattended via a hook (e.g. Stop/SessionStart runs the lint and, on findings, drops a coord todo - NOT a cron/remote scheduler, per feedback_scheduling_via_coord_todo). - Later - automate consolidation with guardrails: auto-apply only high-confidence merges; low-confidence stays a proposal; deletion stays gated regardless. Earn the automation.
Engine already exists: skill .claude/skills/memory-dream/ (+ scripts/memory_dream.py). Cross-machine sync of the repo memory store is handled by .claude/scripts/sync-memory.sh (additive union repo<->harness-profile, SessionStart hook). See also feedback_memory_repo_not_profile if/when written re: the two-store model (repo .claude/memory/ syncs via Gitea; harness ~/.claude/projects/<slug>/memory/ is machine-local and auto-injected).