Frequently asked questions about thinking, epistemology, and cognitive tools. 4568 answers
When one agent finishes and another starts the relevant context must transfer cleanly.
When one agent finishes and another starts the relevant context must transfer cleanly.
When one agent finishes and another starts the relevant context must transfer cleanly.
Identify a transition you make regularly — between deep work and meetings, between planning and execution, between research and writing, between your professional role and your personal life. For the next five days, insert a two-minute hand-off protocol at this transition point. Before you leave.
Assuming that because you are one person, context transfers automatically between your internal agents. It does not. The analytical part of you that spent an hour diagnosing a problem stores its conclusions in working memory, emotional tone, and spatial associations that begin decaying the moment.
When one agent finishes and another starts the relevant context must transfer cleanly.
Draw the dependencies between your agents to see the full coordination picture.
Draw the dependencies between your agents to see the full coordination picture.
Draw the dependencies between your agents to see the full coordination picture.
Draw the dependencies between your agents to see the full coordination picture.
Draw the dependencies between your agents to see the full coordination picture.
Draw the dependencies between your agents to see the full coordination picture.
List every cognitive agent you currently operate — every recurring process, routine, habit, or subsystem that runs on a regular cycle. Aim for at least eight. Now, for each agent, answer two questions: (1) What does this agent need as input before it can run effectively? (2) What does this agent.
Building a dependency map once and treating it as permanent. Your agents change. You add new routines, retire old ones, and shift how they connect. A dependency map from three months ago may describe a system you no longer run. The map is a living document — not a museum exhibit. If you are not.
Draw the dependencies between your agents to see the full coordination picture.
When two agents each wait for the other neither can proceed — design to prevent this.
When two agents each wait for the other neither can proceed — design to prevent this.
When two agents each wait for the other neither can proceed — design to prevent this.
When two agents each wait for the other neither can proceed — design to prevent this.
When multiple agents need the same scarce resource like your attention define allocation rules.
When multiple agents need the same scarce resource like your attention define allocation rules.
When multiple agents need the same scarce resource like your attention define allocation rules.
When multiple agents need the same scarce resource like your attention define allocation rules.
Common patterns like pipeline fan-out and consensus for coordinating multiple agents.