Mental Operating Systems

The self as software... how to debug, patch, and override legacy code.

Architecture of Mental OS

From the moment you wake, layers of routines kick in... automatic beliefs, emotional subroutines and cultural scripts. These legacy programs, written in childhood or inherited from society, govern attention, emotion and behaviour. Without awareness, you run on autopilot, replaying old code when new situations arise.

How Mental OS Runs

Picture a loop where every criticism triggers the same defensive routine, or every stress activates a panic submodule. Those are legacy functions executing without patching. When new input doesn’t fit old code, errors appear as frustration, anxiety or stuckness. Recognising these glitches is the first step toward intentional updates.

Diagnostic Lens: Mental Runtime Diagnostic

This lens identifies recurring automatic routines... your “legacy code”... by logging triggers, default responses and outcomes over 48 hours. Classify each as a core routine, subroutine or glitch to reveal which mental modules need patching or retiring.

Hey! I'm Chris.

I teach smart people how to feel human again.

[The Dirt] Newsletter offers brain-rewiring, metaphor-slinging, self-authorship tools for mental misfits (like you?).

This is not "self help" in any traditional sense. This is the recovery of your agency. Literally.

It's like therapy, but with less crying and more “Oh… that explains everything!”

Subscribe for Weekly Insights into Self-Authorship

This list is small and personal.
Unsubscribe anytime, and your email vanishes like it was never here.
(Yes, really.)
Use your real email.
That’s the one I’m writing to.

A Story of Debugging

When Rajela noticed she always froze at performance reviews, she logged every thought that popped up: “I’m not good enough,” “They’ll find my flaws.” She traced these to a childhood script—Self equals Flawed prototype. In her journal she wrote a patch: “I grow through feedback.” Speaking it first-person... “I grow through feedback”... she practiced it before her next meeting. Over time the old freeze response softened, replaced by curiosity and composure.

A Mini-Workshop: Debug Your Mental OS

Use these steps in real contexts... during a tough conversation, creative block or moment of doubt:

Identify one recurring unhelpful routine you experience today (“I shut down when criticised,” “I rush through tasks”).
Trace the underlying module by naming it (Self equals Legacy routine of Avoidance, Self equals Legacy routine of Hurry).
Patch the code: write a new directive that serves you better (“I pause to learn from feedback,” “I pace my work with purpose”).
Override in the moment by speaking it first-person—“I pause to learn from feedback”—before acting.
Log each trigger and outcome in a notebook, noting shifts in mood, clarity or productivity.

Every conscious override is a software update for your mind.

Collaborative Reflection: Debug Partner Session

Exchange your runtime logs with a partner acting as your debug buddy. Walk through each entry together, asking clarifying questions and suggesting targeted patches. Commit to testing one micro-intervention (a new script or pause ritual) before your next trigger.

Next Steps

Explore the Metaphorical Self and Language as Architecture strategies to reinforce your patches.
Get The Dirt for weekly-ish rambles about how this mind stuff plays out in real life.

Analogy Disclaimer

The computer and operating system metaphor helps reveal how beliefs, habits and scripts run beneath awareness, yet no analogy fully describes the mind’s complexity. You are not literally software, but this lens can guide practical interventions.