The irreducible epistemic atoms underlying the curriculum. 4,828 atoms across 8 types and 2 molecules
Periodically formalize your strongest intuitive schemas by articulating their implicit rules and testing them against evidence, converting speed into inspectability without losing the original pattern recognition.
Surface your implicit person-schemas through explicit audit (default assumptions about motivation, attribution patterns, entity vs. incremental beliefs) rather than treating your perceptions of others as transparent observations of how they really are.
When organizational vocabulary encodes undesired schemas, replace the words deliberately and consistently despite initial awkwardness, because linguistic change drives institutional schema change.
Conduct blameless post-mortems that ask what the team believed about the system rather than who caused the failure, because schema-focused investigation produces structural learning while person-focused investigation produces defensiveness.
Before assuming you understand someone's reasoning, articulate your reading of their underlying model and verify it with them directly.
Listen for what someone mentions first, repeats, dismisses, and treats as obvious — these reveal the structure of their schema more reliably than the content of their arguments.
When you cannot accurately predict what someone will say next from their stated position, your model of their schema is incomplete — update it before arguing further.
Design AI prompts to explicitly frame the task context, provide structural examples, and specify output constraints — these shape the model's temporary processing schema more reliably than abstract instructions.
Test a schema by applying it to edge cases and counterfactuals — schemas that fail at boundaries or cannot handle hypotheticals have structural gaps that will produce errors under pressure.
Document the structural assumptions underlying major decisions so that when reality changes, you can identify which assumptions broke rather than defending the entire decision framework.
When team members persistently disagree despite shared information, map each person's schema explicitly before debating conclusions — most sustained conflicts trace to invisible schema divergence.
Treat early-stage schema errors as cheap and late-stage schema errors as catastrophic — invest in schema validation early when correction costs are lowest.
Version your schemas with dates and track revisions explicitly — visible history of past changes normalizes schema updating and counters cognitive inertia.
Document the purpose each category serves so you can evaluate whether it still serves that purpose when circumstances change.
Break complex classification tasks into hierarchical levels where each level captures information at different granularities, from global patterns down to fine distinctions.
Make category boundaries explicit through written scope notes that specify what belongs and what doesn't, not just labels.
Preserve information through graduated scales during deliberation, then compress to binary only at the final point of action when a decision must be executed.
Match classification granularity to your ability to discriminate and your need to differentiate — scales finer than you can reliably distinguish add complexity without information.
Track classification decisions as hypotheses with version history rather than as immutable facts, enabling systematic improvement of category definitions over time.
Layer facets, tags, or cross-references on top of hierarchical taxonomies to handle items that legitimately span multiple branches, using hierarchy for primary navigation and facets for multi-dimensional access.
Assign types to fields and objects to restrict valid inputs and operations before execution, making entire categories of error structurally impossible rather than detectable after the fact.
Track status as a state within a defined lifecycle rather than as a categorical property, defining valid state transitions and triggers to convert status tracking into executable workflow.
Type items by priority during batch classification sessions rather than at moment of action, converting continuous judgment into categorical lookup that preserves cognitive resources for execution.
Define priority types with one-sentence decision rules that specify membership criteria, not descriptions, ensuring that classification can occur without deliberation about tier assignment.