consolidatelisted

# memory-loop: consolidate Capture and expiry keep memory *flowing*; nothing keeps it *coherent*. Over many sessions the index bloats, two files describe the same thing, an old fact survives next to the newer one that disproved it, and "yesterday" is frozen in a note whose yesterday is long gone. This skill is the operate-stage cleanup: a reflective pass that merges long-tier memory into durable, well-organized form — and, like `remember`, **never writes without your confirmation**. > Adapted from xai-org/grok-build's "dream" consolidation pass (Apache-2.0), > reframed around memory-loop's save gate and tier model. ## When to run It is a manual skill — there is no forced trigger. Run it when: - `MEMORY.md` has grown large (~120+ lines). - A learning-review nudge surfaced duplicate or contradictory notes. - A big piece of work finished and left several related memories behind. ## Scope — what it may touch Read `MEMORY.md` and the `tier: long` memory files beside it. **Exclude:** | Excluded | Why | |----------|-----| | Files without a `tier` key | Outside the lifecycle (the compatibility contract) — never touch them | | `tier: short` memories | The expiry sweep owns these; consolidation leaves them alone | | Identity files (the user/assistant names from `setup`) | Continuity anchors — changed only through the `identity` skill, never here | | Anything already under `archived/` | Already retired | ## The five verbs Review each memory or group through five lenses (the co