The irreducible epistemic atoms underlying the curriculum. 4,828 atoms across 8 types and 2 molecules
When your explanation of your own behavior differs from an external observer's explanation by more than surface framing, treat the divergence as high-confidence evidence of a metacognitive blind spot requiring investigation.
When building knowledge graphs, limit relationship type taxonomies to 5-7 types rather than attempting comprehensive ontological coverage, because classification overhead beyond this threshold produces diminishing informational returns while increasing maintenance cost.
When creating bridge nodes between domains, link to structural patterns (diminishing returns, feedback delays, threshold effects) rather than surface metaphors (companies as bodies), because only structural correspondence enables valid inference transfer across contexts.
When AI systems traverse your knowledge graph, maintain typed relationship labels with explicit predicates rather than relying on semantic similarity alone, because typed edges enable logical reasoning while embeddings only surface associative proximity.
When opening a hub note (one you reference frequently), immediately check its backlinks panel and spend two minutes reading the incoming references to surface connections you had forgotten.
When building connections between notes, test each link by asking whether you can articulate the relationship in a complete sentence—if you cannot, delete the link rather than inflating density metrics artificially.
Identify your top 5% of notes by connection count and schedule quarterly reviews where you verify each hub note is current, accurate, and well-linked, investing maintenance effort proportional to structural importance.
Distinguish real hubs (concepts earning centrality through genuine cross-domain relationships) from artificial hubs (index pages linking to everything in a category) by testing whether removing the hub would sever meaningful conceptual pathways or merely convenience pathways.
Test each bridge node by verifying it generates novel predictions or actionable insights in both connected domains—if it only produces a sense of similarity without bidirectional inference, demote it to metaphor status or delete it.
Identify your three densest knowledge clusters by examining which groups of notes link heavily to each other but sparsely to the rest of the graph, then label each cluster based on observed structure rather than imposed categories.
When a cluster appears only after you force-link unrelated notes to create it, delete those artificial connections because imposed clusters destroy the diagnostic value of emergent structure.
When your graph's cluster structure contradicts your self-narrative about expertise, trust the cluster structure because it reflects actual linking behavior while self-assessment is systematically distorted.
List your major clusters and for each pair ask what connects them; when the answer is 'nothing' or 'one weak edge,' write down the bridge concept that should connect them as your next learning target.
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.