Concepts
The irreducible epistemic atoms underlying the curriculum. 4,828 atoms across 8 types
After completing a relationship map, write what…
After drawing a complete relationship map, write three to five sentences describing the structural story—focusing specifically on what was invisible before you drew the map rather than summarizing what you already knew.
Test schemas at the smallest possible scale first…
Before acting on a schema in any consequential way, test it through concrete action at the smallest possible scale first and observe actual results against pre-stated predictions.
Edge cases that break your schema reveal boundary…
When an edge case breaks your schema, extract the implicit boundary condition that the edge case revealed rather than dismissing the edge case as an irrelevant exception.
Surprise = automatic schema review — do not wait…
Treat surprising outcomes as automatic triggers for schema review rather than waiting for scheduled validation cycles, as surprise signals that at least one schema in your stack has drifted from reality.
After updating a belief, find one decision the new model…
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.
Keep a separate anomaly log with three fields
Create a dedicated anomaly log separate from regular notes where each entry records what you expected, what happened, and which schema generated the expectation.
Log schema changes with 4 fields
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.
Keep schema evolution logs minimal (4 fields) and review…
Maintain schema evolution logs with minimum viable entries of four fields - date, schema affected, what changed, and what prompted the change - reviewed weekly, to generate a dataset about cognitive patterns that introspection alone cannot produce.
Structural schema change is genuine growth; adding…
Measure personal development quality by asking whether any practice changed a schema's structure or merely added information to existing schemas - structural change is genuine growth, information addition is not.
After an insight "clicks," test if you can now…
After experiencing what feels like an insight or integration moment, verify whether it represents genuine integration by testing whether you can now do something you could not do before—if the click produced no new capability, inference, or prediction, you experienced fluency or familiarity rather than structural integration.
When frameworks 'click together,' immediately write what…
After experiencing a moment when previously separate frameworks 'click together', write down specifically what you can now do, see, or infer that was unavailable before the integration—this functional test distinguishes genuine structural integration from mere exposure effects disguised as insight.
Translate every discrepancy into a specific behavioral…
When a feedback loop identifies a discrepancy between current and target state, translate the evaluation into a specific behavioral adjustment for the next cycle rather than stopping at awareness, because learning occurs during adjustment not observation.
When improvement stalls despite effort, shift…
When improvement effort in a domain has stalled despite sustained attention, shift focus from single-loop correction (adjusting actions) to double-loop correction (questioning the framework generating actions) by explicitly listing and testing the assumptions underlying your approach.