obsidian-untangle-knotlisted

# obsidian-untangle-knot ## Core idea In a personal knowledge base, dozens or hundreds of notes end up linking to the same MOCs — that's natural: when you add an article, a book, or a new idea, it's easier to link to the general `[[DevOps]]` than to hunt for the specific sub-map. Over time the general MOC turns from a map into a backlink dump: you open it and drown in noise. Out-links on a hub grow slowly (it's still a **map**, deliberately maintained). In-links grow spontaneously and fast. So the main signal of a tangle is **high in-degree**, not out-degree. The skill: 1. Finds/accepts a hub and counts its in/out links 2. Relies on the hub's **already-existing structure** (subheadings, explicit categories) as ready-made landing points — it doesn't invent new categories when none were asked for 3. Creates a sub-MOC for each category 4. **Main action:** goes through incoming links from resource notes and switches them from the general MOC to the appropriate sub-MOC 5. The original MOC **stays** — it remains the right entry point for the "don't know exactly where to link" case ``` before: after: [hub] (~ stays, but fewer in-links) [hub] ←── 200 in-links ├── [sub-MOC A] ←── 60 in-links (former general ones) ├── 22 out-links ├── [sub-MOC B] ←── 40 ├── [sub-MOC C] ←── 30 └── [sub-MOC D] ←── 25 (general, unclassified ~45 —