Frequently asked questions about thinking, epistemology, and cognitive tools. 4568 answers
Open a note in your knowledge system that you consider a 'hub' — a concept you reference often. Check its backlinks or incoming references. Count how many notes link to it that you had forgotten about. Pick three of those incoming links and read them. Notice what patterns or clusters emerge from.
Building a knowledge system with hundreds of forward links but never consulting backlinks. You dutifully link new notes to existing concepts, but you never open a concept and ask 'what points here?' The graph exists structurally but not experientially — you navigate it in one direction only, which.
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.
Pick one behavior you've been trying to start. Write down the trigger you've been using. Then score it on two dimensions: specificity (could someone else observe the exact moment it occurs?) and observability (do you reliably notice it when it happens?). If either score is low, redesign the.
Using internal states as triggers without calibration. 'When I feel motivated' is not a trigger — it's a wish. 'When I feel anxious' is not a trigger — it's a post-hoc label you apply minutes or hours after the state began. Internal triggers can work, but only after extensive calibration (see.
A trigger must be something you can detect consistently.
Combining multiple trigger conditions for higher-specificity activation.
Pick one behavior you want to activate more reliably. Write the single trigger you currently use (or would use). Now add a second qualifying condition using AND. Then add a third. Test the compound trigger for three days and track: How many times did it fire? How many of those were genuine.
Stacking so many conditions that the trigger never fires at all. You went from 'when I feel stressed' (fires 40 times a day) to 'when I feel stressed AND it is between 2-3pm AND I am at my desk AND my calendar is clear AND I have slept well' (fires zero times a week). Over-specificity kills.
Combining multiple trigger conditions for higher-specificity activation.
You cannot fix what you cannot detect — invest in error detection mechanisms.
Choose one recurring output in your life — a report you write, a meeting you run, a decision you make weekly, a conversation type you repeat. For the next three instances of that output, add a 5-minute detection pass immediately after completion. Do not try to fix anything yet. Instead, write down.
Conflating the feeling that something is wrong with the detection of what is wrong. Vague dissatisfaction is not error detection. It is an unprocessed signal that something in the system has deviated from expectation, but without specificity about what deviated, where it deviated, and by how much..
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.