memory-graph-auditlisted

# memory-graph-audit — pair the user's eyes with the doctor's checks `memory doctor` finds structural issues from code. `memory eval` measures retrieval quality from a question set. Neither catches what's obvious when you open the vault in Obsidian and just look: - Two entities with slightly different spellings that should be merged - A cluster that's weirdly isolated from the rest of the graph - Your name (the vault owner) NOT being central - A customer entity with no champion link - A team page with no member links - Stub files showing up as bright nodes that connect to nothing Computers don't see those things. Humans do. This skill gets the user looking + captures what they see. ## When to invoke - Weekly after the eval-runner runs, as a complement to the numbers - After a big ingest run (new sources connected, new entities created) - When numbers drop but the user can't tell why structurally - One-shot the first time after setup to baseline what the vault looks like ## Pre-conditions - Vault exists at `$MEMORYVAULT_ROOT` - Obsidian is installed and the vault folder is opened in Obsidian (if not, walk the user through opening it once — File → Open vault → pick `$MEMORYVAULT_ROOT`) ## Step 1 — tell the user what to do, then wait ``` Open your vault in Obsidian. Then open the Graph View (Ctrl/Cmd+G or the icon in the left sidebar). For each of the 6 checks below, look at the graph + tell me what you see. Take screenshots if it helps. I'll capture observations a