Mental Fog Reset in Headless Empire OS

The implementation Mike and Arthur use to turn cognitive overload into trusted operating state—and one clear next action.

← Read the Mental Fog concept · Mike's Headless Empire OS

The operating decision

Mental Fog is a trigger protocol, not another permanent journal or parallel productivity system. Mike makes a raw, unedited dump. Arthur sorts it without inventing work. Mike approves the decisions and external actions. The surviving items go into the Headless Empire OS files that already own them.

The raw dump is temporary by default. The processed outcomes become durable.

When to run it

Acute reset

Too many tabs in your head

You feel scattered, behind, indecisive, avoidant, or unable to choose the next useful action.

Shutdown

Mental residue is following you home

Use a five-minute mini-dump to capture anything still tugging before ending the workday.

Recovery

The system no longer feels trusted

Run a full reset after travel, illness, an intense event, a missed shutdown, or several reactive days.

Do not make this mandatory when your mind already feels clear. A ritual intended to reduce load should not become another checkbox that creates load.

The Mike + Arthur loop

Mike dumps without organizing

Text, voice transcription, or a photograph of handwriting. Fragments, worries, ideas, names, obligations, and contradictions are all valid input.

Arthur triages without expanding scope

Arthur identifies decisions, actions, scheduling, delegation, waiting-for items, projects, incubation ideas, and things to drop. Arthur does not turn every thought into a task.

Mike reviews the judgment calls

Mike confirms priorities, deadlines, owners, calendar commitments, delegation messages, and anything sensitive or ambiguous.

Arthur routes approved outcomes

The operating system is updated in the existing source-of-truth files. External tasks, messages, and calendar events remain approval-gated.

Mike starts one next action

Choose the smallest meaningful physical action and, when appropriate, start a RegardingWork focus session. The reset ends in movement, not more planning.

The triage categories

The original four categories—Do, Schedule, Delete, Delegate—are a strong start. Founder work needs a few more destinations, especially Decide and Waiting.

Category	Question	Likely destination
Decide	What unresolved choice is consuming attention?	`decision-log.md` or a decision brief
Do	Is there a concrete action that truly matters now?	`TODAY.md`
Schedule	Does this require a real time commitment?	Calendar, then reference in `TODAY.md`
Delegate	Who should own the outcome?	`delegated.md` plus an approved handoff
Waiting	Has the next move already left Mike's hands?	`waiting-for.md`
Project	Is this a real multi-step commitment?	Existing or justified file in `02-tasks-projects/active/`
Incubate	Is this useful but not committed?	`inbox.md`, backlog, or content ideas
Drop	Would removing this improve focus with little downside?	No OS entry; archive only if history matters

Where items go in Mike's Headless Empire OS

00-command-center/
  TODAY.md                 # what matters now
  WEEK.md                  # this week's outcomes
  NOW.md                   # current strategic context
  inbox.md                 # unclear or unprocessed survivors

02-tasks-projects/
  active/                  # genuine multi-step commitments
  delegated.md             # another person owns the outcome
  waiting-for.md           # the next move is outside Mike's hands
  decision-log.md          # choices that need durable reasoning

03-marketing-content/
  ideas.md                 # ideas that may become public output

06-systems-sops/
  mental-fog-reset.md      # private operating procedure

No separate `mental-ram/` folder

A second inbox would create ambiguity and more maintenance. Mental Fog is the intake and triage layer; the existing Headless Empire OS files remain authoritative.

What Mike sends Arthur

Mental Fog Reset

Here is everything taking up mental space. Treat it as an unedited dump.
Do not invent new work or create external actions yet.

[Paste messy notes, voice transcription, or attach a photo here]

Please return:
1. What may matter today
2. Decisions I am carrying
3. Schedule proposals
4. Delegation proposals
5. Waiting-for items
6. Projects or existing project updates
7. Incubate / drop recommendations
8. The single best next physical action

Mike does not need to make the input readable or complete. Arthur's first job is to reduce the burden, not ask Mike to pre-process it.

Arthur's output contract

Return first

A short synthesis of what is creating the load
The few items that may actually matter today
Explicit decisions and ambiguities
Proposed routing for every surviving item
One recommended next physical action

Do only after approval

Create external tasks or calendar events
Send delegation or follow-up messages
Publish private context to public dashboards or pages
Turn an ambiguous thought into a new active project

Acute reset vs. daily shutdown

During the day

Acute Mental Fog Reset

Dump for up to 10 minutes.
Triage and approve only what matters.
Take three slow breaths or a short physical reset.
Start the chosen action before opening email or chat.

At shutdown

Mental Residue Check

Dump for up to five minutes.
Capture commitments and unresolved decisions.
Set tomorrow's first action.
Stop. The endpoint is permission to recover—not another work sprint.

Privacy and retention

Raw dump: temporary by default; do not automatically store it in Git.
Processed outcomes: store only what improves execution, memory, or a future decision.
Sensitive context: summarize minimally and keep it private.
Public output: never copy private family, health, financial, or business details into public pages without review.
Health boundary: this is an operating workflow, not medical diagnosis or treatment. Persistent or concerning cognitive symptoms deserve appropriate professional attention.

Naming: CEO OS → Headless Empire OS

The public name is now Headless Empire OS. Mike's Headless Empire OS is the private, live implementation; the broader Headless Empire OS is the reusable framework for owner-led businesses.

The existing GitHub repository slug can remain mike-ceo-operating-system temporarily as a legacy technical identifier. Renaming it should be a controlled migration because local folders, Git remotes, multi-machine sync instructions, skills, scripts, and integrations may contain the current path.

Run it now

Send Arthur an unedited dump and say: “Run the Mental Fog Reset. Do not create external actions yet.” Arthur will return the triage, approval questions, proposed OS updates, and one recommended next action.

Read the source concept Explore Headless Empire OS