The irreducible epistemic atoms underlying the curriculum. 4,828 atoms across 8 types and 2 molecules
Record attention allocation in real time using both automated tracking and manual categorization to overcome retrospective estimation bias.
Question the assumptions underlying goals at quarterly intervals, not just whether you are achieving them, because executing a strategy based on falsified assumptions produces tactical success masking strategic drift.
Rotate reflection questions periodically when answers become predictable, because stale questions optimize brain's search path and prevent discovery of novel insights.
Use AI to generate follow-up questions and identify unexamined assumptions in completed reflections rather than to draft reflections, because the insight comes from your mind doing generative work, not from receiving polished analysis.
Conduct pattern analysis by reading multiple review periods in a single session rather than individually, because working memory's 3-5 item limit prevents simultaneous access to temporally separated experiences during daily reflection.
Wait at least 24 hours between experiencing a failure and reviewing it formally, because perceived psychological threat is highest immediately after negative events and this heightened threat systematically reduces the honesty of self-assessment.
When analyzing successes, classify each contributing factor as replicable (within your control) versus contingent (dependent on external circumstances), then extract operational principles only from the replicable factors to avoid attributing controllable outcomes to luck.
Treat energy depletion patterns as leading indicators of burnout rather than productivity decline, because emotional exhaustion precedes output degradation and is only visible through energy/emotion tracking, not task completion metrics.
Design review environments to ensure privacy from external observers, because the knowledge that others might see your reflections activates social self-presentation concerns that systematically distort the honesty of self-assessment toward socially desirable narratives.
Match vulnerable reflections to appropriate containers — share with trusted partners who have psychological safety, relevant context, no competing interests, and proven trustworthiness.
Treat avoidance in reflection as diagnostic data pointing toward the topics most important to your development, not as personal failure to overcome.
Categorize tracked activities by cognitive demand type rather than clock time or task label to reveal attention allocation patterns invisible to narrative memory.
Make undiscussable topics discussable by naming the avoidance explicitly before attempting to engage with the avoided content.
Shift focus from event reflection to system reflection when reviews become repetitive — when current questions produce no new insight, question the level of analysis rather than abandoning the practice.
Focus quarterly reviews on systems and assumptions rather than actions — examine the mental models, beliefs, and structural patterns that generate behavior, not just the behavior itself.
Design tool stack architecture with explicit data flows, defined boundaries, and clear integration points rather than accumulating tools as isolated utilities.
Choose tools whose interface complexity matches the complexity of your need—tools that are too simple force workarounds while tools that are too complex impose unnecessary cognitive overhead.
Designate exactly one authoritative write location for each information type to prevent sync drift and the cognitive overhead of reconciling contradictory copies.
Evaluate tools primarily on whether they reliably perform your specific job-to-be-done, not on feature count or theoretical capabilities you may never use.
Choose tools that store data in open formats (Markdown, CSV, JSON) rather than proprietary formats to preserve data portability and reduce migration risk.
Select tools based on how well they integrate with your existing stack rather than evaluating each tool in isolation, because integration quality determines system-level effectiveness more than individual tool quality.
Push past initial tool competence into proficiency by deliberately practicing capabilities that would expand your effectiveness rather than repeatedly using only the subset you already know.
Train attentional control through repeated detection-and-return cycles rather than attempting to prevent mind-wandering entirely.
Maintain exportable backups of your data in portable formats independent of whether you plan to migrate, to reduce future switching costs.