Apply the scramble test to schema connections…

When two schemas appear to share a concept or principle, test whether the connection is genuine by attempting to scramble the specifics—if the 'connection' would work equally well between any two randomly selected schemas, you've found semantic coincidence rather than structural isomorphism.

When This Fires

When you feel excited about discovering a connection between two schemas or frameworks
During knowledge graph construction when creating cross-domain bridge edges (A bridge node must generate insights in BOTH connected…)
When writing about patterns that span multiple fields
When someone claims two domains "are really the same thing at a deep level"

Common Failure Mode

Connecting schemas through universal concepts like "systems," "patterns," "balance," "growth," or "complexity." These concepts apply to virtually everything, so any two schemas can be connected through them. The connection feels profound but carries no information: it's like noting that two buildings both use "space" — true, uninformative, and not a basis for architectural insight.

The Protocol

(1) When you notice an apparent connection between two schemas, articulate it specifically: "Schema A and Schema B both involve [concept X] in the way that [specific relationship]." (2) Apply the scramble test: replace Schema B with a randomly selected third schema. Does the connection still work? (3) If the connection survives scrambling → it's too general. The connecting concept is universal rather than specific to these schemas. Don't create a bridge edge. (4) If the connection breaks under scrambling → it's specific to these two schemas. Investigate further — this may be genuine structural isomorphism worth documenting. (5) For genuine connections, verify bidirectional inference transfer (A bridge node must generate insights in BOTH connected…) to confirm the structural bridge is load-bearing.