compass-integritylisted

# Compass Integrity Check ## Overview Compass writes a Merkle hash chain over project memory and a per-session drift signal. Both can be silently broken — a chain mismatch means a memory file was edited outside the writer; a drift-red session means the past assistant output diverged from intent. **A recall hit on tampered or red-drift memory is worse than no recall**. This skill runs the integrity checks **before** the user commits to acting on memory. ## When to invoke Trigger conditions (any one): 1. User says "do we remember", "did we discuss", "based on past sessions" — they're about to lean on memory. 2. User points at a specific memory file or session ID — verify the chain covers it cleanly. 3. Drift incident already suspected ("why did the assistant flip on X?", "this looks like a regression") — pull recent drift history. 4. Session start in a project with memory/, before any recall fires — preflight. 5. After a crash, conflict resolution, or merge — chain may have been broken by a non-writer edit. Skip when: - The work is purely procedural (no memory dependency). - The user explicitly said "ignore memory" / "don't use prior context". ## How it works The skill is a one-pass orchestrator over four already-shipped CLIs in this plugin: | Check | Tool | What it tells you | |-------|------|-------------------| | Daemon liveness | `nc 127.0.0.1 9876` ping | Is BGE-m3 up? If not, recall is metadata-only. | | Chain integrity | `compass_verify.py` | Are any memory fil