The irreducible epistemic atoms underlying the curriculum. 4,828 atoms across 8 types and 2 molecules
When contradiction surfaces between beliefs, expand schema structure to hold both beliefs simultaneously, then migrate reasoning to the evolved schema before contracting the old incompatible framework.
Version schema changes explicitly by recording old schema, new schema, triggering contradiction, and date—creating a changelog that documents thinking evolution rather than obscuring it.
Build structural accountability systems that surface contradictions automatically rather than relying on introspective motivation, because directional motivation flexibly adjusts evidence thresholds to favor preferred conclusions.
Build explicit connections between schemas to create a coordinated knowledge system rather than maintaining isolated mental models that fire independently.
Resolve contradictions between schemas before attempting integration—unacknowledged contradictions propagate through every connection you build.
Your default cognitive machinery works against genuine coherence through distortion, avoidance, and rationalization—real coherence requires deliberate effort to integrate rather than merely rationalize.
Abstract domain-specific knowledge into domain-agnostic structure before attempting transfer—concrete practices don't transfer, but structural patterns do.
Look for structural isomorphisms between domains, not surface metaphors—metaphors import misleading surface features while isomorphisms preserve only relational structure.
Build a unified theory that describes how you actually behave, not how you wish you behaved—the theory must match observed behavioral data, not aspirations.
Cluster schemas by underlying structure rather than by domain or surface features—structural duplicates reveal redundancy that domain organization obscures.
Create named abstractions for structurally identical schemas across domains, then link domain-specific instances to the abstraction rather than deleting them.
Verify structural similarity before merging schemas—surface similarity can mask critical differences in agency, power dynamics, or mechanisms that must be preserved.
Test newly abstracted schemas in domains not represented in the original cluster—if the abstraction generates useful insight in novel contexts, it captures real structure.
Structure integration work to address foundational gaps before attempting to connect higher-order schemas, because missing prerequisite concepts silently degrade everything built on them.
When attempting total schema integration simultaneously, either abstract frameworks to meaninglessness or force-fit distortions; instead, integrate in connected pairs and small clusters first.
Allow periods of genuine disorientation between integration stages rather than forcing immediate coherence, because frameworks transitioning from subject to object require time to restructure.
Revisit core concepts at progressively higher levels of abstraction and connection rather than attempting full integration on first encounter.
When schemas resist integration despite repeated attempts across multiple stages, diagnose for contradictory foundations, competing resource claims, or scale mismatch before continuing.
Document both the released schema and the conflict that necessitated its release, creating an evolution log rather than performing erasure.
Run bounded experiments operating without a schema before formally releasing it, testing whether framework coherence improves and whether essential capabilities are lost.
Map cross-domain structural similarities by identifying shared relational patterns rather than surface feature resemblances when seeking cross-pollination opportunities.
When a cross-domain mapping breaks down, investigate the mismatch systematically rather than forcing the analogy, because mapping failures reveal domain-specific structural features.
Deliberately juxtapose schemas from different domains in writing, mapping core concepts and relationships to create conditions for structural parallels to become visible.
When self-schemas generate competing recommendations in a decision, construct a higher-order schema that defines their relationship rather than choosing one schema over the other.