The irreducible epistemic atoms underlying the curriculum. 4,828 atoms across 8 types and 2 molecules
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.
Before high-stakes observations (meetings, decisions, analyses), write down your current mood and strongest expectation about the outcome to make perceptual filters visible for later comparison against actual observations.
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.
Set three random timers throughout your workday; when each fires, pause for 30 seconds to scan jaw, shoulders, chest, stomach, and hands for tension, rating each 1-5 and noting your current activity.
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.
When you encounter the same judgment arising across three or more different contexts, treat it as a structural cognitive habit requiring explicit examination rather than a series of independent assessments, because cross-context repetition indicates the judgment is executing from pattern-matching rather than situation-specific analysis.
For habitual judgments that fire too quickly to intercept before they execute, implement a marking protocol where you log each occurrence with 'HJ' notation immediately after noticing it, because marking converts the judgment from invisible background process to observable object without requiring the neurologically impossible task of preventing automatic activation.
When noticing a habitual judgment about a person or group, apply the substitution test by asking whether you would make the same evaluation if a different person or group were in the identical situation—if the answer is uncertain or negative, you have detected a judgment running on identity rather than behavior.
When building new observation skills, construct a five-level difficulty hierarchy ranging from trivial annoyances to identity-level triggers, then spend minimum one week at each level before progressing, because attempting high-stakes observation without low-stakes mastery produces reversion to automatic judgment under pressure.
When practicing observation at any difficulty level, stay at that level until the trigger becomes boring rather than advancing on a fixed schedule, because boredom signals that automatic judgment has been replaced by automatic observation at that complexity level.
When using AI to practice observation skills, provide it with your written accounts of charged situations and explicitly request separation of observational statements from evaluative statements, using the AI's output as immediate feedback on which judgments you embedded without noticing.
When a behavior, reaction, or outcome recurs three or more times across a 30-day period, classify it as a pattern candidate requiring structural analysis rather than treating it as coincidence.
Record each occurrence of a suspected pattern with date and context in a dedicated log before drawing conclusions, because memory-based frequency assessment systematically overestimates recurrence through the frequency illusion.
Name behavioral patterns using 2-4 word descriptors that compress the full trigger-response sequence into a recognizable label, enabling real-time pattern recognition under cognitive load.
For each named pattern in your Pattern Dictionary, document three required fields: the pattern name, its observable trigger conditions, and the default behavioral response it produces.
Do not expect pattern recognition alone to eliminate the pattern—track the ratio of pattern-following to pattern-breaking instances over weeks rather than demanding immediate control, because automaticity requires repeated override practice to weaken.
Before building optimization systems around a personal correlation, test whether the correlation survives when you control for potential confounding variables through deliberate experimental variation.
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.
For each genuine success in the past two years, document conditions present, behaviors that differed from defaults, people involved, internal state, and 48-hour setup—then surface elements appearing in three or more instances as your replicable success pattern.
When a problem persists across multiple attempts, identify exceptions where the problem was absent or reduced rather than analyzing why the problem occurs, as exception conditions are more directly actionable than problem mechanisms.
Cross-reference your success pattern elements against your upcoming project plan before starting work, building in the overlapping conditions deliberately rather than hoping they emerge, as replication requires engineering.
Project each daily pattern forward using compound math (what does 365 repetitions produce?) before deciding whether to maintain or change it, because linear intuition systematically underestimates exponential outcomes.
Audit your daily pattern portfolio by labeling each recurring behavior as appreciating (+), depreciating (-), or neutral (=), then make exactly one trade per month (reduce one depreciating pattern by 50%, install one appreciating pattern at minimal scale).