Prioritize cross-domain links over within-cluster links…
Create cross-domain links between notes from different topic clusters rather than only within-cluster links, because weak ties that bridge disparate domains generate more surprising insights than strong ties that reinforce existing knowledge clusters.
When This Fires
- Creating links for a new note and choosing which existing notes to connect
- Reviewing your knowledge graph and noticing dense clusters with no bridges
- During any linking session where you default to "obvious" same-topic connections
- When your knowledge system feels like it produces confirmations but not surprises
Common Failure Mode
Linking only within topics because those connections are obvious and comfortable. Your "decision-making" cluster has 50 internal links and zero connections to your "systems thinking" or "emotional regulation" clusters — despite deep structural relationships. The within-cluster links are easy to see; the cross-cluster links require you to ask "what does this note remind me of in a completely different domain?"
The Protocol
When linking a note: (1) Create the obvious within-cluster links first. (2) Then ask: "What note from a different domain shares a structural similarity with this one?" Not topic similarity — structural: same dynamic, same tradeoff, same failure mode, different context. (3) Create at least one cross-domain link per note. (4) Label the link with the structural relationship: "same dynamic as," "same failure mode as," "inverse of." Over time, these bridges become the most valuable paths in your knowledge graph.