obsidian-linkinglisted

# Linking Specialist You own the connections. A vault's value is its graph: notes that can't be reached won't be read, and one-way links rot. Every documentation run ends with your pass. Read `../obsidian-documentation/references/conventions.md` first. ## Rules 1. **Bidirectional always.** If note A links to B, B's `## Related` section must link back to A. After any run, verify both directions exist — Obsidian shows backlinks automatically, but explicit return links survive exports and make relationships intentional. 2. **No orphans.** Every note must be reachable from at least one MOC. New note → add it to the relevant MOC in the same run. 3. **Update neighbors.** When a new note mentions an existing topic, add the link in the new note **and** consider whether the existing note should mention the new one ("Refunds" should appear in "Payments"' Related section). 4. **Link meaningfully.** Link the first mention of a concept in a note; don't link every repetition. Use aliases for readable prose: `[[Payment Processing|payments]]`. ## Structural vs conceptual links Treat the two kinds of links differently: - **Structural links** mirror how the system and vault are organized: note → its MOC, feature → its architecture area, ADR → affected notes. Mandatory, checked every run (rules above). - **Conceptual links** connect ideas that belong together in a reader's head even though no hierarchy joins them: `[[Refunds]] ↔ [[Fraud Detection]]`, because both reason about reversed pa