The irreducible epistemic atoms underlying the curriculum. 4,828 atoms across 8 types and 2 molecules
Abstraction necessarily discards information from the reality it represents, retaining only selected features deemed relevant while eliminating detail.
Abstract representations that lack connection to concrete, embodied, or perceptual experiences become unstable and lose meaning under cognitive load or when transferred to novel contexts.
The level of abstraction at which you construe a situation (high-level why versus low-level how) changes what features appear relevant and what actions feel immediately available.
When encountering the same insight expressed in three or more separate notes across different contexts, extract the shared structural pattern into a single canonical note with a precise name, then replace the duplicate instances with links to the canonical abstraction.
When considering whether to merge two similar notes, test whether the underlying structure is identical (same entities, same relationships, same claims) rather than whether the vocabulary overlaps, because structural identity warrants abstraction while surface similarity does not.
Validate cross-domain pattern candidates by verifying that the relational structure (not surface similarity) matches across domains—two patterns share structure when the causal relationships between elements are preserved even when the elements themselves differ completely.
When identifying meta-patterns, require each second-order claim to ground in at least three documented first-order pattern instances to distinguish genuine meta-patterns from intellectual speculation.
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.
Before beginning any communication, writing, or presentation, state in one sentence what you are trying to accomplish, then use that purpose statement to select the appropriate level of abstraction.
When stuck on a problem for more than 30-60 minutes at your current level of abstraction, force yourself to spend at least 5-10 minutes at an adjacent level (one step more abstract or one step more concrete) before continuing.
When creating bridge nodes between domains, link to structural patterns (diminishing returns, feedback delays, threshold effects) rather than surface metaphors (companies as bodies), because only structural correspondence enables valid inference transfer across contexts.
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.