Distinguish real hubs (genuine cross-domain centrality) from artificial hubs (index pages with bulk links)
Distinguish real hubs (concepts earning centrality through genuine cross-domain relationships) from artificial hubs (index pages linking to everything in a category) by testing whether removing the hub would sever meaningful conceptual pathways or merely convenience pathways.
Why This Is a Rule
Not all high-connection notes are genuine hubs. A "Cognitive Science — Index" page with 50 links to every note in the cognitive science folder has high connection count but no conceptual centrality — it's a directory, not a hub. Remove it and every linked note is still reachable through other paths. A genuine hub like "Feedback Loops" has high connection count because multiple domains independently link to it through meaningful conceptual relationships — remove it and those cross-domain pathways are severed.
The distinction matters for maintenance allocation (Invest quarterly maintenance in your top 5% most-connected notes — they are your graph infrastructure): real hubs deserve quarterly review because they're structurally load-bearing. Artificial hubs are convenience infrastructure that can be maintained less frequently or auto-generated.
The removal test separates the two: if removing the note would sever meaningful conceptual pathways (real hub), it's structural infrastructure. If removing it would only sever convenience pathways that could be replaced by a search (artificial hub), it's a directory.
When This Fires
- When identifying which notes are your graph's "true hubs" for prioritized maintenance
- During graph analysis when connection count alone doesn't distinguish important from merely connected
- When evaluating whether a high-connection note deserves intensive review
- During knowledge system architecture review
Common Failure Mode
Treating index pages as genuine hubs: "This note has 80 links, so it's our most important note." Connection count measures connectivity, not conceptual centrality. An index page has many connections because it was designed to link to everything — not because many concepts genuinely depend on it.
The Protocol
For each high-connection note: (1) Mentally remove it. (2) Ask: "Would removing this note sever meaningful conceptual pathways — paths where the hub's concept is the actual bridge between otherwise disconnected domains?" (3) If yes → real hub. The concept itself (not just the note) is structurally central. Invest in maintenance. (4) If only convenience pathways are lost (navigational shortcuts, categorical listings) → artificial hub. Maintain as convenience infrastructure, not as critical architecture.