The irreducible epistemic atoms underlying the curriculum. 4,828 atoms across 8 types and 2 molecules
Tag beliefs and schemas in your knowledge system with explicit confidence levels and evidence bases, then review and update these calibration tags over time.
Before significant decisions, state your confidence level explicitly along with the three strongest reasons you could be wrong to institutionalize calibrated thinking.
Separate prediction accuracy from decision quality by building contingency plans for multiple outcomes rather than assuming your most likely prediction will occur.
Record your mental and physical state alongside predictions to detect correlations between physiological/emotional states and systematic prediction errors.
When communicating information across time or people, explicitly record the context that shaped your interpretation to prevent systematic misunderstanding by future interpreters who will lack that context.
When switching between cognitive contexts, insert a deliberate transition protocol that closes the old context and loads the new one, rather than assuming instantaneous context transfer.
Record decision context—forces, constraints, alternatives, emotional state—in writing at the moment of choice, before hindsight bias can reconstruct a fiction that feels like memory.
When experiencing cultural friction or confusion, treat it as data about the boundary of your own operating system rather than as evidence of others' incompetence.
Apply temporal context filters to distinguish between domain-specific facts (short half-life, requires aggressive updating) and structural principles (long half-life, validated by temporal survival).
Review consequential assessments in at least two distinct emotional contexts before finalizing to reveal what each emotional state makes visible or invisible.
For high-stakes vocabulary in agreements or decisions, request operational definitions from each stakeholder independently before proceeding to verify alignment.
Move from abstract agreement to concrete specification by requesting examples and counter-examples when stakeholders use high-stakes abstract nouns.
When technical vocabulary crosses disciplinary boundaries, explicitly verify that terms carry the same operational meaning in each discipline before using them in cross-functional work.
Before sending text-based messages, re-read as if you are a stranger with zero shared context to detect ambiguities that shared history would otherwise mask.
When receiving ambiguous messages, respond with clarifying questions about missing context rather than constructing interpretations from your own context.
When frustrated by individual behavior in organizations, identify at least three structural factors that reward or permit the behavior before attributing it to character.
Design organizational processes by asking 'What will a rational person optimize for under these incentives?' rather than 'What do I hope people will do?'
When evaluating performance, ask 'What did the system make easy or hard?' before asking 'What did this person do well or poorly?'
Break complex cognitive work into convergent blocks (analytical, detail-oriented, evaluative) and divergent blocks (creative, associative, generative), then configure distinct physical environments optimized for each mode rather than attempting all cognitive work in a single workspace.
Before group discussions on important topics, require participants to write down their positions privately, then compare post-discussion positions to identify when conclusions changed due to new evidence versus social absorption.
Introduce a single designated dissenter in group decisions to reduce conformity pressure by approximately 80%, particularly when consensus is forming rapidly around a position.
Deliberately expose yourself to epistemic communities outside your primary professional circle on a regular schedule to prevent your social environment from becoming the sole determinant of what you can believe.
Document the reasoning and context behind decisions alongside the decisions themselves in persistent systems that survive personnel turnover, treating rationale as equally important as the decision record.
Before proposing the removal of any inherited system, process, or structure, first document why it was originally created and what problem it solved—if you cannot reconstruct this context, you lack sufficient information to safely remove it.