EN NL
← Sleep ← Overview DMN →
Brain Mechanism 16 of 19

Working Memory

Small active buffer vs vast long-term store.

What is it

Working memory is the brain's scratchpad. It holds the small amount of information you're actively thinking about right now — typically 4 to 7 items. It's what you use when you hold a phone number in your head while walking to find a pen, or when you keep track of the ingredients you've already added to a recipe.

Working memory is fundamentally different from long-term memory. Long-term memory is vast, durable, and mostly unconscious. Working memory is tiny, fleeting, and fully conscious. The relationship between them is like the relationship between a desk and a warehouse. The desk is where you do your work. The warehouse is where everything is stored. You constantly move things between the two, but the desk can only hold so much at once.

The capacity limit of working memory is not a design flaw. It's a feature. By limiting what can be active simultaneously, the brain forces prioritisation. You can't think about everything at once, so you must choose what matters right now. This constraint is what makes focused thought possible.

What it does in the brain

Working memory is maintained by sustained neural firing in the prefrontal cortex. Unlike long-term memories, which are stored as stable synaptic patterns, working memory items are kept alive by neurons that literally keep firing — a costly, energy-intensive process. This is why maintaining focus is tiring. Your prefrontal cortex is burning energy to keep those neurons firing.

When working memory is full and a new item demands attention, something must be evicted. This happens automatically and often below conscious awareness. You're holding three facts in mind, a fourth arrives, and one of the original three silently drops away. This is why interruptions are so destructive to complex thought: each interruption evicts something from working memory that must be laboriously reloaded from long-term storage.

The interaction between working memory and long-term memory is bidirectional. Working memory pulls items from long-term storage (remembering a fact), processes them (combining facts to reach a conclusion), and then writes the result back to long-term storage (learning something new). It's the active workspace where thinking happens.

What it does in ThetaOS

This mechanism is being explored for ThetaOS. The question is: should the system have a concept of "currently active" versus "stored but dormant"? Currently, every query treats the entire 309-table database equally. There is no distinction between information that's contextually relevant right now and information from a decade ago.

A working memory layer would give Tom a "desk" — a small, fast context of what's currently being discussed, recently mentioned, or contextually relevant to the current conversation. Instead of searching the entire database for every query, Tom would first check the working memory buffer and only reach into long-term storage when the buffer doesn't have the answer.

Consider a conversation about an upcoming meeting with Peter Ros. A working memory system would load Peter's dossier into the active buffer at the first mention. Subsequent questions about Peter — "when did we last meet?" "what did we discuss?" "is he connected to anyone at that organisation?" — would be answered from the buffer, not from a fresh database scan each time. The conversation would feel natural and flowing, the way talking to a person with a good memory feels natural — they don't pause to look up each fact because the relevant context is already on their mental desk.

This is not yet built. Tom currently has conversation context (what's been said in this session) but not true working memory (a curated set of entities and connections loaded proactively based on context). The difference is significant: conversation context is passive (what was mentioned), while working memory would be active (what's likely to be needed). Building this requires predicting relevance, which requires understanding context — the hardest problem in personal knowledge management.

Exploring