The irreducible epistemic atoms underlying the curriculum. 4,828 atoms across 8 types and 2 molecules
Break interpretive narratives into observable facts and acknowledged inferences to separate what occurred from what you constructed around it.
Audit behavioral systems for contextual dependencies before disruption occurs, as the number and type of dependencies predict fragility under specific disruption categories.
Reduce activation energy of habits to near-zero for fallback versions, as disruption depletes the cognitive resources required to overcome high initiation costs.
Design modular routines where each component can execute independently, as monolithic chains create cascading failure when any single element is disrupted.
Identify the essential function each routine serves and design minimum viable versions that preserve that function with minimal infrastructure, rather than compressing the same activities into less time.
Pre-design and test minimum viable routines during periods of abundant cognitive resources, as depleted capacity during disruption prevents effective real-time adaptation.
Maintain behavioral continuity during disruption by firing habit loops at minimal intensity rather than suspending completely, as pathway maintenance requires activation not magnitude.
Define non-negotiable minimum behaviors for each major routine that execute regardless of circumstances, maintaining habit pathways even at microscopic scale.
Explicitly suspend non-essential routines during crisis rather than letting them fail, to prevent guilt from compounding stress.
Design graduated restart sequences in advance of disruptions, because decision-making capacity is lowest precisely when restart protocols are needed.
Restart behavioral systems by sequentially loading one habit per day rather than simultaneously restarting all behaviors, to respect depleted self-regulatory resources.
Deliberately seek interpretations from positions that differ along dimensions of perspective, heuristic, or predictive model to surface information your position structurally cannot access.
Begin behavioral restart with the keystone habit that creates conditions for other habits, not with the habit you feel most guilty about neglecting.
Prohibit guilt from the restart process because self-criticism produces avoidance rather than action, extending disruption duration.
Start restarted habits at 30-50% intensity and escalate gradually over 3-5 days rather than attempting full intensity immediately.
Use gradual restart protocols for disruptions lasting more than 5-7 days, because beyond that threshold habit automaticity decays measurably.
Default to gradual restart when uncertain, because failed full restarts trigger abstinence violation effects while unnecessary gradual restarts cost only time.
Treat every disruption as a stress test that reveals which behaviors are identity-anchored versus environment-dependent versus streak-dependent.
Design habits with flexible execution parameters (time windows, location options, intensity ranges, sequence independence, functional substitutes) while maintaining fixed core functions to enable sustained performance across variable conditions.
Identify and reduce context dependencies in important habits by auditing which specific conditions (equipment, location, time, people, technology) must be present for behavior execution and designing alternatives for high-disruption-probability dependencies.
Design a context-independent behavioral core of 3-5 practices completable in under 5 minutes with zero dependencies that maintain continuity during worst-case disruptions while full-featured habits remain the primary growth mechanism.
Separate behavioral function (the purpose a behavior serves) from form (the specific implementation) and design multiple forms that deliver the same function under different constraints.
Structure feedback processes to collect observations from roles with different functional positions, incentives, and information access to systematically reduce shared blind spots.
Conduct a structured disruption debrief within 48 hours of recovery mapping timeline, survival audit, root cause analysis, recovery analysis, and specific system modifications to convert disruption experience into architectural improvements.