Ground every abstraction with 3+ examples from different…
Connect each abstract concept in your knowledge system to at least three concrete examples from different domains, because single examples invite surface-feature overgeneralization while multiple examples force attention to shared structural patterns.
When This Fires
- Adding an abstract concept note to your knowledge system
- Reviewing concept notes that feel vague or hard to apply
- When a concept seems clear in one domain but you can't apply it elsewhere
- Complements Test understanding by generating three examples… (three-domain example test for understanding verification)
Common Failure Mode
Three examples from the same domain: "feedback loop in software: CI pipeline, monitoring alerts, A/B test iterations." These all share software surface features, so the abstraction remains domain-bound. The fix: one software example, one biological example, one organizational example. The diversity forces the structural pattern to surface.
The Protocol
For each abstract concept in your system: (1) Check: how many concrete examples are linked? From how many domains? (2) If fewer than three from different domains → add examples. Ask: "Where else does this structural pattern appear?" (3) Each example should instantiate the concept's core mechanism in a different domain. (4) The concept note becomes the hub; the examples become the spokes. Future retrieval works through any spoke, and understanding deepens at the hub where diverse spokes converge.