Concepts
The irreducible epistemic atoms underlying the curriculum. 4,828 atoms across 8 types
Actively search for absent relationships in your maps…
Actively search for absent relationships in your maps by asking what connections should exist but do not, because missing links are often more informative than present ones.
Externalize all relationships in a system simultaneously…
Externalize all relationships in a system simultaneously through visual mapping to reveal structural patterns that sequential analysis cannot detect.
Look for hub nodes with disproportionately many connections…
Look for hub nodes with disproportionately many connections in your relationship maps, because they create both vulnerability to targeted disruption and resilience to random failures.
When reasoning about indirect connections between entities…
When reasoning about indirect connections between entities, explicitly verify that the relationship type supports transitive inference rather than assuming all chains propagate.
Design propagation systems with explicit damping factors…
Design propagation systems with explicit damping factors that reduce signal strength at each hop to prevent unstable accumulation in circular paths.
When evaluating information received through a chain…
When evaluating information received through a chain of recommendations or endorsements, multiply the confidence values at each hop rather than treating endpoint confidence as equal to any single link.
Concentrate redundancy investments at nodes and connections…
Concentrate redundancy investments at nodes and connections where failure consequences are highest rather than distributing uniformly across all system components.
Test backup systems periodically under realistic conditions…
Test backup systems periodically under realistic conditions to verify they can actually substitute for primary systems when needed.
When designing critical systems, ensure backup paths…
When designing critical systems, ensure backup paths do not share failure modes with primary paths by using independent implementations, physical separation, or diverse technologies.
Identify system bottlenecks by running removal tests…
Identify system bottlenecks by running removal tests that ask which single node or connection failures would make specific functions impossible rather than merely slower.
When queues consistently form at specific points…
When queues consistently form at specific points in a system, trace upstream to find the constraint where processing capacity is exceeded by arrival rate.
Use spatial layouts in visualizations to make relationship…
Use spatial layouts in visualizations to make relationship patterns available to perception rather than requiring serial cognitive computation.
When creating knowledge graphs from notes or documents…
When creating knowledge graphs from notes or documents, maintain multiple independent access paths to important concepts rather than relying on a single organizational taxonomy.
Construct relationship maps manually before using AI tools…
Construct relationship maps manually before using AI tools to generate them, as the cognitive benefit comes from making explicit decisions about entities, connections, and types rather than consuming finished artifacts.
Map from memory first before consulting sources to surface…
Map from memory first before consulting sources to surface the gaps between your mental model and reality, as these gaps reveal precisely where understanding is incomplete.
When relationship maps grow beyond 20-30 nodes, introduce…
When relationship maps grow beyond 20-30 nodes, introduce hierarchical abstraction by treating clusters of densely connected nodes as single units at higher levels.
When evaluating system resilience, count the number…
When evaluating system resilience, count the number of independent paths between critical nodes as this number equals the system's tolerance for node failures along those paths.
Address bottlenecks by increasing the constraint's capacity…
Address bottlenecks by increasing the constraint's capacity or by distributing its load across parallel paths rather than optimizing components that are not constraints.
Organize information into parent-child structures where each
Organize information into parent-child structures where each parent summarizes its children and each child specifies its parent, enabling navigation by choosing your level of detail.
Identify and operate at the 'basic level' of your domain's…
Identify and operate at the 'basic level' of your domain's hierarchy — the level where categories carry maximum information with minimum cognitive effort.
Break information into chunks of 3 to 5 items at each level…
Break information into chunks of 3 to 5 items at each level of a hierarchy, using nested grouping to extend effective processing capacity beyond raw working memory limits.
When explaining or communicating, explicitly match…
When explaining or communicating, explicitly match your level of abstraction to your audience's purpose and current need rather than your own cognitive comfort zone.
When stuck on a problem, shift abstraction levels…
When stuck on a problem, shift abstraction levels deliberately: drill down when you need mechanism and specifics, zoom out when you need context and patterns.
Frame tasks concretely (how will I do this?) rather…
Frame tasks concretely (how will I do this?) rather than abstractly (why does this matter?) to reduce procrastination and increase immediate action.