1. Brain dump
Write everything on your mind: tasks, worries, spouse asks, car noise, client emails, dentist, random half-ideas. Don’t organize. When you think you’re done, keep writing — another layer always surfaces.
Dump cognitive load in ~10 minutes, then keep mental RAM clear so flow can show up on a Tuesday afternoon
← Productivity · Personal · Headless Empire OS · Our live implementation · Send and delete
Shared in this form by @mogulinfluence (“clear 80% of your mental load in 10 minutes if you run this EXACTLY tonight”) — x.com/i/status/2078488145964806529
Full value and protocol come from Rian Doris (@RianSweetDoris), flow-state educator / Flow Research Collective — original long-form: x.com/i/status/2052805993759666603 (article on cognitive load, flow, and the dump protocol).
This page is a practical rewrite for implementation — especially with a markdown / agent OS like Headless Empire.
That nagging sense that something needs a reply, a call, a decision — but you can’t hold it all at once. Part of your mind keeps scanning while you try to work. Rian frames this as cognitive load: working memory as mental RAM. Too many tabs open → everything slows.
Two performer types: the overburdened brain (always behind, sloppy late work, frantic energy) vs the unburdened mind (same responsibilities, but captured externally — brain free to process, not store).
Paper + pen preferred. Handwriting helps “cognitive offloading” (visual + motor cortex transfer burden out of working memory).
Write everything on your mind: tasks, worries, spouse asks, car noise, client emails, dentist, random half-ideas. Don’t organize. When you think you’re done, keep writing — another layer always surfaces.
Scan each line and decide:
Capture alone isn’t enough. Until each item has a fate, the brain keeps tugging.
Fold the paper; put it out of sight. Three breaths: in 3, hold 2, out 10. Then go straight to the most important task — no email, no phone — use the clear window immediately.
The fastest way to speed up your brain is to slow down and get everything out of it.
A dump is a deep clean. Kitchens don’t stay clean without daily habits. Three rules:
| Block | Time | What you do |
|---|---|---|
| Review goal stack | ~15 min | Year / quarter / month goals. What moved last week? What’s the gap? What closes it? |
| Next week’s actions | ~30 min | Max 3 goal-directed actions (not 20). Put them on the calendar, not a floating list. |
| Peak hours | ~45 min | Block high-energy time for those three. Pre-decide so the week doesn’t re-open “what should I do?” every hour. |
Kills background anxiety of “am I on the right thing?” — a huge hidden load for founders running multiple companies.
| Step | Time | What you do |
|---|---|---|
| Tomorrow’s Big Three | ~5 min | 1–3 goal actions on tomorrow’s calendar with time blocks. |
| Clear goals breakdown | ~5 min | For each: 3–5 ultra-specific first steps in the calendar note (flow trigger: no startup fog). |
| Clear the decks | ~5 min | Email triage (2-min rule / schedule / archive). Mini brain dump of open loops. Close tabs, clear desk. |
Unfinished tasks create the Zeigarnik effect — brain treats them like unpaid bills overnight. Power-down is the “all clear” so work doesn’t commute home in your head.
Headless Empire is a markdown / agent-friendly operating system for running companies (full OS notes). Use it as the external RAM so your brain isn’t the database.
We tested the architecture against Mike's live operating system and made one important change:
do not add a second mental-ram/ folder. The raw dump is a temporary intake;
approved outcomes route into the command center, calendar, delegation, waiting-for, decisions, and
existing project files.
We also added Decide and Waiting to the original Do / Schedule / Delete / Delegate categories. Those two unresolved states create a large share of founder cognitive load.
See the complete Mental Fog Reset inside Mike's Headless Empire OS →
After a handwritten or spoken dump, give the raw input to Arthur/Claude/Codex and ask it to sort the items without inventing new work. The agent proposes routing and one next action; you still own priorities, decisions, external tasks, calendar commitments, and delegation messages. This aligns with low-load multi-agent work and harness habits: systems hold state; you process.
| System | Role in clearing fog |
|---|---|
| Headless Empire OS | External brain for multi-company ops — dump lands here, not in mental RAM |
| Send and delete person | Delegate bucket that actually leaves your head |
| Productivity goals | Feeds the weekly goal stack review |
| Mike's Headless Empire OS implementation | Leadership layer: fewer open loops at the top |
| Company Brain | Team-level capture so knowledge isn’t trapped in heads |
| Calendar (real blocks) | Where “schedule it” becomes true — lists alone don’t release loops |
Peak performers aren’t those who hold the most. They’re those who refuse to hold it in working memory.
The exact Mike + Arthur triage, approval, routing, and next-action workflow.
See the implementation →When agents own loops, your head stays clearer — if the harness holds state.
Read →Protocol credited to @RianSweetDoris · shared via @mogulinfluence · original long-form here.
Comments
Approved comments appear below. Log in once with GFAVIP — it applies across the whole site. GFAVIP login
View comments archive