memory-gatelisted

# Memory Gate The Memory-First Gate and its investigation protocol, extracted from the `memory` router per ADR-063 (memory-skill decomposition). `memory` still routes here; an agent about to change an existing system loads this sub-skill instead of the full memory surface. The gate is one operation with a single rule: before you change something that already exists, search memory for why it exists. The search uses the canonical Tier 1 script; this sub-skill owns the enforcement semantics (ADR-070) and the Chesterton's Fence framing, not the search implementation. ## Triggers Use this skill when the user says: - `memory-first gate` to apply the BLOCKING pre-change check - `search memory before changing` to recover historical context first - `chesterton fence check` to investigate why a system exists before removing it ## Memory-First Gate (BLOCKING) Before changing existing systems, you MUST: 1. Search memory for the topic you are about to change. 2. Review results for historical context. 3. If Tier 1 is insufficient, escalate to Tier 2 (episodes). 4. Document findings in your decision rationale. 5. Only then proceed with the change. ```bash # Recover the "why" before you change the "what" SCRIPTS_DIR="${COPILOT_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-.claude}}/skills/memory/scripts" python3 "$SCRIPTS_DIR/search_memory.py" "[topic]" ``` **Why BLOCKING**: under 50% compliance with "check memory first" guidance when it is advisory. Making it BLOCKING achieves 100% complianc