Task Stack
Updated 2026-08-10
INTRODUCTION
English translation pending.
CORE DEFINITION
The Task Stack applies the last-in-first-out discipline of a program stack to human interruption management: when interrupted, the current task is pushed with a record of its context, the interruption is handled, and the suspended task is then popped and resumed. Its core proposition is that context, not time, is the scarce resource during interruptions, so explicitly saving state preserves the ability to resume efficiently. The key qualifier is stack depth: a deep stack means the oldest tasks are not resumed for a long time, and a push without a recorded context is not a real save.
SCAFFOLDING EFFECT
Reduce cognitive load
- State capture: write down exactly where you are and what comes next before switching. - Interruption handling: process the inserted task and then pop back rather than drifting onward. - Depth watch: cap how many tasks can sit suspended before you force a return to the base.
Anchor fast decisions
Resuming an interrupted task requires reconstructing the mental state that was lost, and reconstruction is slower and more error-prone than the interruption itself. Recording the state at the moment of interruption converts that reconstruction into a cheap read. The stack discipline ensures the most recent suspension is resumed first, which matches how recently used context is still partially active.
MINIMUM ACTION
In progress 0/1Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- en.wikipedia.orghttps://en.wikipedia.org/wiki/Stack_(abstract_data_typeverified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS