A bridge node must generate insights in BOTH connected domains — one-way similarity is just metaphor
Test each bridge node by verifying it generates novel predictions or actionable insights in both connected domains—if it only produces a sense of similarity without bidirectional inference, demote it to metaphor status or delete it.
Why This Is a Rule
A genuine bridge node connects two domains through shared structure that enables inference transfer in both directions. "Diminishing returns" as a bridge between engineering and education should generate insights in both: engineering insights about education ("adding more teachers per student follows diminishing returns like adding servers to a cluster") AND education insights about engineering ("educational scaffolding suggests onboarding new engineers through graduated autonomy"). Bidirectional generation confirms the structural bridge is real.
A metaphor generates a sense of similarity in one direction without enabling genuine inference: "Learning is like building a house" — you can vaguely map foundation → basics and walls → intermediate concepts, but this produces no novel architectural insights and no novel educational insights. It's a one-way aesthetic mapping, not a structural bridge.
The bidirectional test separates generative bridges from decorative metaphors: can the bridge produce actionable insights you didn't have before, in both connected domains? If not, it's a metaphor wearing a bridge costume.
When This Fires
- During knowledge graph quality audits when evaluating cross-domain links
- After creating a bridge node and wanting to verify it's genuine
- When a cross-domain connection "feels insightful" but you're not sure it's substantive
- Complements Bridge domains through structural patterns, not surface metaphors — only structure enables inference transfer (structural vs metaphorical bridges) with a specific validation test
Common Failure Mode
Accepting one-directional insight as validation: "This bridge helped me understand education through an engineering lens!" But can it also help you understand engineering through an educational lens? One-directional insight is a helpful metaphor but not a structural bridge. The bridge must work both ways.
The Protocol
For each bridge node: (1) Ask: "What novel prediction or insight does this bridge generate in Domain A?" Write it down. (2) Ask: "What novel prediction or insight does this bridge generate in Domain B?" Write it down. (3) If both → genuine structural bridge. The shared pattern enables bidirectional reasoning. Keep and invest in the connection. (4) If only one direction → useful metaphor but not a structural bridge. Demote: keep as an associative link but don't rely on it for cross-domain inference. (5) If neither → decoration. Delete.