The irreducible epistemic atoms underlying the curriculum. 4,828 atoms across 8 types and 2 molecules
Before attempting to update a deeply-held schema, explicitly restate it as 'I hold the belief that [X]. This belief is a model I use. It is not who I am.' to create cognitive distance between identity and the belief.
After updating a belief, identify one downstream decision where the revised model produces a different recommendation than the old one to ensure the update becomes operational rather than merely verbal.
When updating a schema, map all downstream dependencies (habits, commitments, tools, relationships, routines) before implementation and migrate high-friction dependencies first.
Before finalizing any schema update, list five situations where the old schema produced accurate results and verify the new schema handles all five to ensure backwards compatibility.
Set a tolerance window of at least sixty seconds to sit with cognitive dissonance before attempting resolution, as premature resolution systematically favors existing schemas over new evidence.
When a schema has many downstream dependencies, apply slower and more deliberate revision cadences than its pace layer alone suggests, because updating foundational schemas requires cascading updates to all dependent schemas.
Write schema evolution log entries with four mandatory fields - date, schema affected in original language not current interpretation, specific triggering evidence or encounter, and the replacement belief - to defeat hindsight bias through fixed external records.
For each evolved schema, document not just old and new versions but also what the old belief was protecting or enabling, because identifying the lost function reveals emotional costs of revision and increases honesty about unrevised beliefs.
When schema conflict persists after examining evidence, build a conditional routing rule specifying the exact conditions under which each schema applies rather than attempting to pick a universal winner.