Frequently asked questions about thinking, epistemology, and cognitive tools. 4568 answers
New agents are most fragile in their first month — they need extra attention and support to survive.
Track versions of your agents so you can compare, rollback, and learn from changes.
Choose one agent you actively use — a decision-making heuristic, a weekly review process, a communication protocol, a problem-solving routine. Write down its current form as v_current (assign whatever version number feels right based on how many times you think it has changed). Then reconstruct.
Versioning without actually preserving the old version. Slapping 'v2' on your current process while letting v1 fade from memory defeats the entire purpose. If you cannot retrieve the previous version and compare it side-by-side with the current one, you have version labels but not version control..
Track versions of your agents so you can compare, rollback, and learn from changes.
Periodically review and rebalance your agent portfolio — retire underperformers, invest in high-value agents.
Documentation should evolve with the agent — outdated docs are worse than no docs.
Pick one agent or automated system you currently maintain. Open its documentation — README, wiki page, inline comments, whatever exists. Read every factual claim: data sources, triggers, dependencies, output destinations, failure modes. For each claim, mark it as current, outdated, or unknown..
Writing documentation once at creation and never touching it again. You'll know you're in this failure mode when someone asks how an agent works and you say 'check the docs' without confidence that the docs reflect reality. The second failure mode is more subtle: updating the agent's behavior but.
Documentation should evolve with the agent — outdated docs are worse than no docs.
The way you create, maintain, and retire agents mirrors how you learn, practice, and let go of knowledge. Recognizing this parallel turns agent management into a form of self-directed development.
You need capture tools available in every context where you think — desk, commute, shower, conversation, bed. A gap in coverage is a gap in your thinking.
Map every context where you regularly think: desk, commute, walking, shower, bed, meetings, gym, cooking. For each one, write down your current capture tool and how many seconds it takes to go from thought to externalized text (or voice). Any context over 10 seconds is a leak. Any context with no.
Choosing a capture tool because it's powerful rather than because it's present. The person who picks Obsidian as their only capture tool and leaves it on their laptop will lose every thought they have away from their desk. Capability is irrelevant if the tool isn't within arm's reach when the.
You need capture tools available in every context where you think — desk, commute, shower, conversation, bed. A gap in coverage is a gap in your thinking.
When writing is impossible, speaking into a recorder preserves the thought. Your voice is a capture tool — and in high-friction moments, it is the only one fast enough.
Not all connections are equally strong — quantifying strength improves your model.
Writing does not record thinking. Writing IS thinking. The act of externalization transforms a vague internal sense into something precise enough to inspect, challenge, and build on.
Writing does not record thinking. Writing IS thinking. The act of externalization transforms a vague internal sense into something precise enough to inspect, challenge, and build on.
Take a decision you're currently stuck on. Write out every consideration, option, and fear — one per line. Don't organize. Just dump. Then read it back as if a colleague wrote it. Notice what you see that you couldn't see when it was all in your head. The gaps, contradictions, and missing pieces.
Treating externalization as documentation rather than thinking. If you externalize after you've decided, you're recording. If you externalize while you're deciding, you're thinking. The timing determines the value. Most people wait too long.
Writing does not record thinking. Writing IS thinking. The act of externalization transforms a vague internal sense into something precise enough to inspect, challenge, and build on.
Metacognition — the ability to observe your own thinking — is what makes self-correction possible. Without it, you cannot debug your own reasoning.
Metacognition — the ability to observe your own thinking — is what makes self-correction possible. Without it, you cannot debug your own reasoning.