Letter #1: The Gift of Mental Space

Built with AI. No CS degree.

Pain

For years, I lived alone with my white cat, Simba. There was a background process running in my head back then. It never slept. Not when I was deep in code. Not when I was laughing with friends. Not even at night, with Simba curled against my chest, breathing slow and warm.
It was a quiet whisper: If I didn’t wake up tomorrow, who would know she was there?
I lived alone. Simba had no backup human. No spare key holder who checked in daily. No family nearby who’d notice my absence within hours. It was just the two of us — a closed loop of mutual dependence. And that loop had a single point of failure.
This wasn’t dramatic fear. It wasn’t the kind of anxiety that stops you from living. It was worse than that — it was the kind that quietly steals your ability to be here now. Every moment of peace with Simba came with a faint, unspoken asterisk: enjoy this, but don’t forget — if I vanished, she would starve.
I used to think this was just me being neurotic. Overprotective. But the more I talked to other solo pet owners, the more I realized: this is a shared low-grade hum of dread. A background process most of us never learned to kill.

Insight

This feeling wasn’t weakness. It wasn’t sentimentality. It was a genuine systemic gap — a Single Point of Failure in the architecture of my life back then.
In software, a single point of failure is anything whose loss brings the whole system down. A server that handles all traffic. A database with no replica. An API key with no backup.
In my life, the single point of failure was me.
Traditional solutions exist, but they’re not systems — they’re hopes. A neighbor who “promises to check.” A sticky note on the fridge. A relative who lives three hours away. These all depend on human memory, human attention, human inconsistency. They’re prayers, not protocols.
And prayer is not a system.
The real insight was this: the anxiety wasn’t the problem. It was a symptom. The problem was a design flaw in how I’d structured my life back then. I needed to close that gap — not by worrying less, but by designing a system that made worry unnecessary. That worry from those years later became Keeper.

Struggle

I tried asking a neighbor to check on Simba, but she would forget. I wrote a note and stuck it on the fridge, but it just became part of the background noise. I tried sending periodic messages to a friend to report that everything was okay, but it felt like a burden on them. None of it worked. I needed a system, not someone’s goodwill.

Action

I’ve since moved. I no longer have a pet.

But the worry from those years didn’t move with me — it became something else.

I built Keeper.

Keeper wasn’t the first app I shipped — I’d already shipped two before it, Tellmelist and Yes or No, both practice runs for learning how to build with AI. But Keeper was the first one I built for myself.

I’m not a traditional programmer. I’m a non-programmer who uses tools like Claude Code to build real things. Keeper was that: a digital emergency contact system for people like me.

The concept is simple: a timer that resets every time I interact with my phone. If I don’t check in within a set window (24 hours, by default), Keeper sends an emergency message to a designated contact — with feeding schedule, vet info, and a note to check on the pet.

I’m not going to pitch you the features. You can find those at Keeper’s App Store page. What I want to tell you is what happened after I built it.

The background process stopped.

Not entirely, at first. But gradually. The first night I knew, truly knew, that the worry from those years had a system-shaped answer — that was the first night in years I felt something I’d almost forgotten.

Mental space.

That’s the gift. Not the app. Not the features. But reclaiming the cognitive real estate that had been occupied by a single question: What if I don’t come home?

But that question — and building Keeper to answer it — is what got me hooked on building. One app became two, became a habit, became a way of living.

This is what sovereignty looks like for me: not control over everything, but closing the most important gaps so I can surrender to the rest.

If you’re carrying a background process that keeps you from being present, you know the hum. You don’t have to carry it. Keeper was the first instance of that pattern for me.

That feeling of peace — when the loop is closed and the system is running — that’s sovereignty.
This is Letter #1 of The Sovereignty Letters. Each week, one letter on designing a life of sovereignty — from system design to intentional craft to the art of being your own maker.
Subscribe →
Stay Sovereign.