The irreducible epistemic atoms underlying the curriculum. 4,828 atoms across 8 types and 2 molecules
Understanding another person's reasoning structure and mental states (cognitive empathy) is neurologically and functionally distinct from feeling what they feel (affective empathy).
Write with causal language (because, therefore, leads to) and insight language (realize, understand, recognize) when processing difficult experiences, because this linguistic structure forces transformation from raw venting to structured sense-making that produces measurable health benefits.
When a thought triggers resistance to capture (a 'flinch' away from writing it down), use that resistance feeling as the capture trigger rather than a reason to skip—thoughts that produce hesitation are the highest-value capture targets.
Defer emotional interpretation to review sessions when multiple entries enable pattern recognition, rather than explaining emotions during initial capture.
After emotionally charged interactions—difficult conversations, stressful emails, frustrating exchanges—take three minutes to write what happened, what you felt, and what (if anything) needs to happen next before switching to analytical work.
When experiencing the urge to switch tasks during focused work, pause for three seconds to name the internal state driving the urge (boredom, uncertainty, anxiety), then consciously return to the task without suppressing the emotion.
When receiving critical feedback, insert a physical pause (close laptop, stand up, or wait 90 seconds) before responding to allow prefrontal cortex engagement rather than amygdala-driven reaction.
In emotionally charged messages, draft your reactive response first in a private document, then wait 10 minutes before composing the actual message, using the comparison between versions as data about emotional distortion.
When using AI to draft difficult communications, compare your reactive draft against the AI-generated neutral version to measure where emotions are distorting your message, rather than sending the AI version directly.
After initial defensive emotional reaction to feedback, name the specific emotion with high granularity ('I notice frustration about the timeline comment, not the technical critique') before responding, to activate prefrontal regulation.
When you feel chest tightening or jaw tension during a design review or technical discussion, write down 'I notice I want to protect [X]' before formulating your response to create separation between observation and defense.
Before sending difficult emails or presenting challenging conclusions, run your draft through fact-story filtering by asking which statements would survive if you had to prove them with timestamps, screenshots, or measurements, because this prevents narrative from masquerading as evidence.
When multiple relationships produce the same tension pattern despite different people, map your own contribution to the dynamic before attributing the pattern to others' behavior.
For each avoided task that persists beyond 48 hours, log the emotion triggered, the substitute activity performed, and the rationalization constructed, as these three elements constitute the replicable structure of personal avoidance patterns.
When information triggers strong emotion, restate it with all emotionally loaded language stripped before evaluating whether the neutral version warrants the reaction the framed version produced.
When angry, deliberately seek disconfirming evidence and independent risk assessments, as anger systematically inflates certainty, deflates risk perception, and increases risk-seeking behavior.
When using AI during high stress, prompt with 'I am stressed and may be experiencing tunnel vision—what am I likely not seeing?' rather than 'prove my interpretation is right.'
Frame feedback requests as specific behavioral questions ('What do I consistently do that I probably don't realize?') rather than character evaluations to keep feedback at task level instead of identity level.
When emotional content must be conveyed via text, state the emotion explicitly ("I'm frustrated about X") rather than relying on word choice or punctuation to convey tone, because textual cues for emotion fail approximately 45% of the time.
After labeling each emotion, write one sentence identifying what is generating it using causal language ('because'), then check for emotional layers by asking 'What is underneath this?' to surface masking dynamics.
When externalizing emotions, avoid narrative venting ('he did this and then that happened') and instead use structured labeling ('I feel X because Y') to convert fusion into defusion.
Use AI to analyze patterns across multiple emotional externalization entries (recurring emotions, triggers, trends) rather than to label emotions for you, because the regulatory benefit comes from the act of labeling, not from being labeled.
Capture feedback within 60 minutes of receiving it using structured fields (date, source, verbatim content, emotional reaction, specific behavior) before memory reconstruction distorts the signal.
When a schema triggers defensiveness at the suggestion of testing it, treat that emotional response as a diagnostic signal of high psychological investment requiring especially rigorous validation.