Context Preservation Systems
The Problem
Every context switch without preservation has a cost. Estimates vary, but commonly cited:
- Gloria Mark (UC Irvine): 23 minutes to return to original task
- Self-reported (monotropic): 30-60 minutes for deep work recovery
- Some sessions: Never recover—the thread is lost
For monotropic individuals, this cost may be higher because the cognitive context is deeper.
What is "Context"?
Context is everything you're holding in working memory during a task:
Technical Context
- Files open
- Cursor position
- Tab arrangement
- Terminal state
- Git branch
- Recent changes
Cognitive Context
- Current hypothesis
- What you just tried
- What you're about to try
- Why you're doing this
- Constraints you're working within
- Dead ends already explored
Emotional Context
- Momentum/flow state
- Confidence level
- Frustration accumulation
- Engagement level
Technical context can be saved. Cognitive context is harder. Emotional context may not be recoverable.
Preservation Strategies
1. Breadcrumb Notes
Before any interruption, write one sentence:
"Debugging auth flow - token expires before refresh, checking middleware next"
Takes 10 seconds. Saves 30 minutes on return.
2. JSON State Dumps
Structured format for complex sessions:
{
"task": "Fix payment webhook",
"hypothesis": "Signature validation failing due to raw body parsing",
"tried": ["body-parser", "express.raw()", "manual Buffer"],
"next": "Check if Stripe sends different content-type in test mode",
"files": ["webhook.ts:142", "payment.service.ts:89"],
"blockers": ["Need Stripe CLI to test locally"],
"confidence": "medium"
}
3. Session Logs
Automatic capture of session activity:
- Commands run
- Files modified
- AI interactions
- Commit messages
Enables reconstruction even without explicit notes.
4. Voice Memos
"I'm in the middle of refactoring the auth system. I just finished the login flow and I'm about to start on password reset. The tricky part will be the email verification because..."
Lower friction than typing. Can be transcribed later.
Tool Support
What Helps
| Tool | How it helps |
|---|---|
| IDE session restore | Reopens files, tabs, cursor positions |
| Git stash | Saves work-in-progress without commit |
| tmux/screen | Terminal sessions persist across disconnection |
| Obsidian/notes | Quick capture with low friction |
| AI with history | Can reference earlier in conversation |
What Doesn't Help
| Anti-pattern | Why it fails |
|---|---|
| "I'll remember" | You won't |
| Browser tab explosion | Too much context, can't find anything |
| Undifferentiated notes | Capture without structure = hard to use |
| Starting fresh | Loses all momentum |
Intervention Results
Before Context Preservation System
- Average recovery time: 45-60 minutes
- Session recovery rate after interruption: ~30%
- Lost threads per week: ~5-10
After Implementing Preservation
- Average recovery time: 10-15 minutes
- Session recovery rate after interruption: ~70%
- Lost threads per week: ~1-2
Caveat: Single case study. Individual results vary.
Implementation Recommendations
Minimum Viable Context Preservation
- One note per active task (even just a file name)
- Breadcrumb before interruption (10 seconds)
- Reopen yesterday's session (IDE feature)
Full Context Preservation System
- Structured state dumps (JSON format)
- Automatic session logging (commands, files, AI)
- Regular checkpoint commits (git, even WIP)
- Voice memo fallback (when typing is too much friction)
- Review ritual (start of day: where was I?)
Open Questions
- Can context preservation fully eliminate switching cost?
- What's the minimum viable preservation that's actually used?
- How does AI with long context windows change this?
- Is there a "context debt" that accumulates across days?
Contribute your own preservation systems or data on what works.