The irreducible epistemic atoms underlying the curriculum. 2,888 atoms across 3 types and 2 molecules
When scanning incoming messages with a defined goal, ask whether each item directly serves that goal—if yes process it, if no skip/archive/batch it—and do not evaluate whether it's 'interesting' or 'might be useful someday.'
Process one information source at full depth (notes, connections, could-explain-to-others) per week rather than ten sources at surface level to build signal detection capacity in your critical domains.
Use AI to scan peripheral domains weekly and deliver filtered summaries, while reserving human attention for 2-3 deep engagements per week in your core signal domains.
Before opening any social media platform, write down your specific intended information target and set a 5-minute timer; when the timer fires, close the app regardless of whether you found the target.
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.
For each important outcome you care about, identify one lagging indicator (the outcome) and pair it with 1-2 leading indicators (upstream behaviors that predict it), tracking both to validate the predictive relationship.
When a leading indicator improves but its paired lagging outcome does not follow within the expected timeframe, treat the leading indicator as broken (gamed, confounded, or non-predictive) and replace it.
Before claiming to understand a complex topic, generate at least three concrete examples from different domains that instantiate the concept, and if you cannot produce varied examples, treat this as evidence that you have acquired vocabulary without understanding.
After each information fast, document three specific categories: inputs you genuinely missed, inputs you craved but didn't need, and inputs you forgot existed, then eliminate or downgrade items in the latter two categories.
Schedule quarterly depreciation reviews where you scan captured notes and bookmarks for information that has exceeded its useful life, then either update with current data, archive with context, or delete entirely to prevent outdated information from corrupting current decisions.
After consuming any piece of information, write one connecting sentence that relates it to existing knowledge using the structure 'This connects to [X] because [Y]'; if you cannot write this sentence within two minutes, classify the content as non-compounding noise regardless of its intrinsic quality.
During expertise development, explicitly document both what you now prioritize and what you have learned to ignore, as conscious articulation of ignored features is the operational test of signal efficiency.
When expert pattern recognition locks onto a familiar solution, force consideration of alternatives by asking 'I see X—but what if it is not X? What would I expect if it were Y?' before committing.
For decisions under genuine ambiguity, impose a mandatory 48-hour waiting period before acting unless you can specify concrete significant costs of delay.
Write explicit tripwire conditions specifying what observations would resolve ambiguity in each direction before entering any strategic waiting period.
Execute all identified cuts during the audit session itself rather than creating a deferral list, as audit outputs are decisions implemented immediately not intentions documented for later.
When using AI for signal detection, provide explicit goals and evaluation criteria first, then use AI to scale pattern recognition, because AI without human-defined goals produces generic output from noisy channels.
When angry, deliberately seek disconfirming evidence and independent risk assessments, as anger systematically inflates certainty, deflates risk perception, and increases risk-seeking behavior.
Deploy 5-minute cyclic sighing (prolonged exhalations at ~6 breaths per minute) before difficult meetings or after stressful news to reverse stress-induced perceptual narrowing.
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.'
When making frequency or probability estimates, pause and ask: 'Am I estimating actual frequency, or how easily I can picture this?' then look up the base rate before deciding.
Before any consequential decision, populate two mandatory fields: the recent event driving current feeling, and the base rate/historical trend across the full relevant time window.
When a vivid individual case makes you feel certain about probability, explicitly ask 'what is the actual frequency of this event in the relevant population?' before forming any judgment.
Frame pre-mortem prompts as 'It is [future date]. This has failed completely. Write why.' rather than 'What could go wrong?' to shift cognition from speculation to explanation.