Frequently asked questions about thinking, epistemology, and cognitive tools. 3434 answers
Document your process for managing knowledge — not just the knowledge itself. Your system should be explicit enough that you could rebuild it from documentation alone.
The discomfort of a failing schema is data not damage.
The discomfort of a failing schema is data not damage.
The act of mapping relationships generates new insights about the system. You do not map what you already understand — you map in order to understand. The diagram is not a record of finished thinking. It is the medium in which thinking happens.
Too detailed is as unhelpful as too abstract — match the level to your current need.
Too detailed is as unhelpful as too abstract — match the level to your current need.
Revising a model in response to evidence is the defining act of a strong thinker. The refusal to update is not confidence — it is cognitive debt accumulating interest.
List your most important schemas so you can maintain and improve them systematically.
When A links to B, B should know that A links to it — bidirectional linking reveals hidden patterns.
Natural groupings in your knowledge graph show you what you know most about.
When two of your beliefs conflict, the contradiction itself tells you something important. It reveals that your knowledge has grown beyond the neat consistency of a closed system and is encountering the productive tensions that drive genuine understanding. The discomfort of holding conflicting.
What is true at one level of abstraction may not be true at another — check which level each claim operates at.
Your collection of schemas should work together without conflict. Coherence is not agreement — it is the absence of unresolved contradiction, where each schema strengthens rather than undermines the others.
Connect what you know about work with what you know about relationships health and creativity. Domain boundaries are administrative conveniences, not real walls. The schemas you build in one area of life contain structural insights that transfer to every other area — but only if you deliberately.
Good integration preserves the diversity of your schemas while connecting them.
Every agent has a trigger that activates it, a condition that validates it, and an action it takes.
A trigger must be something you can detect consistently.
A trigger must be something you can detect consistently.
Combining multiple trigger conditions for higher-specificity activation.
Combining multiple trigger conditions for higher-specificity activation.
You cannot fix what you cannot detect — invest in error detection mechanisms.
You cannot fix what you cannot detect — invest in error detection mechanisms.
Asking why five times in succession usually reaches the root cause of a problem.
Small uncorrected errors can trigger chains of increasingly large errors.