The irreducible epistemic atoms underlying the curriculum. 2,888 atoms across 3 types and 2 molecules
Show a portion of your knowledge graph to someone with domain expertise and ask what's missing to detect unknown unknowns that your graph's topology cannot reveal through internal inspection alone.
Start building your knowledge graph with your current five nodes rather than waiting for critical mass, because a graph with five nodes and eight edges already delivers more value than five hundred isolated notes.
Apply Shneiderman's three-phase visualization protocol to graph exploration: overview first without reading labels, zoom and filter to examine specific clusters, then details-on-demand for individual nodes.
Use AI to identify conspicuously absent concepts that would bridge multiple existing graph nodes rather than generic topic recommendations.
When external knowledge structures stop being actively traversed, maintained, and integrated into daily reasoning, treat them as degraded assets rather than cognitive extensions.
Deliberately link contradicting ideas in your knowledge graph rather than keeping them in separate domains, because spatial proximity forces the cognitive confrontation that compartmentalization prevents.
When measurement data shows stable satisfactory performance with no identifiable bottleneck, redirect optimization effort to a different system rather than continuing to optimize the current one.
Apply the cascade test to contradictions by asking 'If I resolved this, what else would have to change?' to distinguish surface contradictions (low dependency count) from deep contradictions (high dependency count).
Set holding periods for contradictions based on cascade depth: one week for low cascade, two to four weeks for medium cascade, one month or longer for high cascade.
During a contradiction holding period, write brief notes whenever the contradiction surfaces capturing what triggered it and what you noticed, without attempting resolution.
When holding period ends, extend the hold rather than forcing resolution if you cannot yet articulate a missing variable or synthesis, because premature resolution defeats the purpose of incubation.
Audit the last seven days of actual behavior (calendar, screen time, spending, energy allocation) against each stated value to calculate revealed preferences, scoring alignment from 1-10.
When discovering that behavior contradicts stated values, investigate the actual reward structure driving behavior rather than increasing willpower or restating values more emphatically.
For each identified values-behavior gap, ask what competing value the behavior actually reveals and what would need to change in environment, habits, or defaults for alignment.
Test whether a resolved contradiction is genuine innovation rather than compromise by verifying that both original requirements are fully satisfied, not partially abandoned.
Design early warning indicators for polarity drift by identifying the characteristic downsides of each pole, then monitor for those downsides to trigger course-correction before crisis.
Before aggregating data across subgroups, check whether the relationship holds within each subgroup independently, as aggregate patterns can reverse at the disaggregated level (Simpson's paradox).
Label each belief in your knowledge system with validity windows specifying the time period during which the belief held, converting apparent contradictions across time into explicit version transitions.
Before attempting to resolve any persistent organizational tension, apply the problem-vs-polarity test: can new information or analysis make one side permanently win? If no, design oscillation management rather than searching for resolution.
When two credentialed experts contradict each other on the same question, treat their disagreement as a map of genuine uncertainty in the evidence base rather than as a problem requiring you to pick a winner.
When experts disagree, ask 'why do they disagree' rather than 'who is right' to identify structural sources like different methodologies, populations, or outcome measures.
Address contradictions at the strategic principle level rather than re-adjudicating them at each tactical decision point to prevent decision multiplication.
When steel-manning an opposing position, verify adequacy by checking whether advocates of that position would say 'Yes, that is exactly what I mean' before proceeding to critique.
When articulating your core operating principles, require that each principle explain your actual observed behavior patterns rather than aspirational values, because a unified theory must match behavioral data not wishes.