← ClaudeAtlas

coalwashlisted

Memory washer/defragmenter for agent memory — two lanes: class-B (memory+governance) cleans the FAT, never the MEAT; class-A (transcripts) is byte-identity-only. Fidelity-first: a free mechanical Quick pass + a CODE gate blocking any STRUCTURED-token drop by diff; the paid Full pass is a separate consent; every DELETE/MERGE is plan-sourced + snapshot-backed. Session-start gauge; Fat hysteresis arms OBESE (auto-Quick, standing config, never asks). FULL = the economic cut-point (break-even proven, numbers shown): force-runs Quick; still over → one wizard ask, re-armed on growth. A capacity wall also forces FULL (wash-if-fat, else externalize). NO calendar cadence — never loop it. A manual `/coalwash` runs a fat-only, muscle-reorg, or estate pass. localOnly = Quick-only, no sub sees memory content. Honest: slows memory-overhead growth, does NOT eliminate it. Triggers: "/coalwash", "clean memory", "defrag memory", a [CoalWash] band nudge. Cross-agent (Claude Code validated). Zero-dep, offline, no API keys.
TheColliery/CoalWash · ★ 11 · Code & Development · score 79
Install: claude install-skill TheColliery/CoalWash
# CoalWash — the memory washer > **Fidelity scope — CLASS-B wash tiers only** (class-A estate = the byte-identity contract two notes down): the gate PROVES every STRUCTURED token that went in came out (the classes at step 3) by mechanical diff; it CANNOT SEE survivors trading places (`pass 878/fail 0` → `pass 0/fail 878` passes it) — re-pairing + load-bearing **prose** facts are the semantic reviewers' + YOUR job, never the gate's. Deletes ride the adjudicated plan, not a separate approval; safety is the transactional apply (snapshot → whole-run rollback; a rollback whose own restore fails reports **partial**, never a silent mixed state). CoalWash **slows** memory-overhead growth — it does not eliminate it. > [!CAUTION] > Fat grows at a different rate per project ��� a schedule cleans lean memory, and past fat-exhaustion a semantic pass can throw away something load-bearing (prohibitions #1–2). A looped Full tier re-pays semantic cost every round for nothing, and accumulates over-compression pressure. > **Class-A estate (ULTRA + RE-TIER's byte lane) — a DIFFERENT, STRONGER contract:** transcripts/tool-results are vendor-owned + machine-parsed (fail the 4 wash tests) → **NEVER semantic-edited**; the guarantee is **byte-identity** (copy-verify-then-delete, `estate-restore` round-trips) — not the structured-token gate above. The seams where the class-B gate re-enters = RE-TIER's hot-index rewrite + choice 4's ③ manual-tier work (fidelity gate + MOVE-VERIFY + #54 anchor bind e