Working Memory File
| Category | Productivity / Personal Tools |
| Origin | Dave Paola, ZK note (Dec 2024); podcast episode |
| Surfaced in OS | Mar 8, 2026 (imported from ZK) |
Core Concept
Keep a plain text file on your desktop called working memory.txt. Open it in a plain text editor (TextEdit on Mac, plain format — no fonts, no bold, nothing). Throughout the day, use it as an extension of your brain.
Type things in so you don’t have to hold them in your head:
- Four key points from a presentation
- Notes and action items from a meeting
- Tracking tasks as you clear your inbox
- Anything you need to remember in the next 30 minutes
Write as fast as you can type. Don’t organize. Don’t format. Just dump. The file is ephemeral — it exists to keep your working memory clear, not to be an archive.
Why It Works
The brain has limited working memory slots (roughly 4-7 items). Every item you hold in your head reduces capacity for actual thinking. A plain text file is the lowest-friction way to offload items: no app to open, no structure to maintain, no sync to worry about.
Plain text is the point. No formatting means no friction. No app means no distraction. No structure means no overhead.
Connection to This OS
Dave’s Operating System is the strategic layer — persistent knowledge, patterns, people, projects. working memory.txt is the tactical layer — what’s in your head right now, this minute. The two are complementary:
- working memory.txt = volatile, ephemeral, cognitive offload
- This OS = persistent, structured, strategic memory
The pattern echoes the OS’s design philosophy: plain text as the universal primitive, composition over enclosure, tools that layer rather than replace.
Related Patterns
- Context Over Interface — the value is in the content, not the tool
- Integration vs Composition — working memory.txt composes with everything; it doesn’t integrate with anything