The Whole Point
Doug is asleep on the floor next to my chair.
He's a Shih Tzu. Twelve pounds of attitude with a face that looks permanently mildly offended. He'll be awake in twenty minutes and he'll have opinions about it.
Two months ago I didn't have a dog.
Two months ago I didn't have time for a dog.
Now I do.
This article is about why.
Most people in IT know this rhythm. The work is the day. The day is the work. You wake up and the alerts are there. You go to bed and the alerts are still there. Someone is always pinging you. Something is always on fire. The infrastructure you built to make life easier becomes the thing that owns your life.
I did this for over twenty years. Worked the kind of jobs where "on call" meant "always." Built stacks at home because work wouldn't let me build them right. Then spent my evenings maintaining the stacks I built at home because nobody else was going to. The hobby became the second job. The second job ate the first job's leftovers.
Most decent hackers I know are still living this way. They built the homelab to escape the corporate grind and now the homelab is the new grind. They built the AI assistant to save time and now they spend an hour a day prompt-engineering it into not lying to them.
The infrastructure consumed the operator. Same story, different decade.
When I started bringing AI into the workflow seriously, not as a chatbot toy but as actual delegation, the math changed.
The trilogy I wrapped up a couple weeks back (articles 17, 18, 19) was about how to do this without it blowing up in your face. Governance. The 70/30 model. Captain's mark before anything fires. AI does the 70 that was eating the day. Human keeps the 30 that actually matters... decisions, judgment, voice, risk acceptance.
That's the technical version.
Here's the actual version.
The 70 is the part that was never supposed to be your life. The 30 is the part that was always the point.
The 70 is documentation, initial drafts, research sweeps, scaffolding, boilerplate. The stuff that fills the day but doesn't define the work. The stuff that takes a competent human eight hours and an AI station forty seconds.
The 30 is the decision. The judgment. The vote. The taste. The "no, that's wrong, here's why." The thing that can't be delegated because it's the thing that makes you you.
When you actually run this model, not as a slogan but as a working principle, something happens that nobody talks about.
You get your freakin day back!
A few weeks back the call came in.
Mom got hit. Scam attempt that almost worked, browser hijacker that did. She's tech-savvy enough to recognize when something is wrong but not tech-savvy enough to fix it on her own. So she called.
I spent an hour on the phone trying to fix it blind. You know the drill. "What does the screen say now?" "Click the X in the top right corner." "No, the OTHER top right corner." "Okay, can you read me what's in the URL bar?"
It should have been a five-minute job. It wasn't. And the whole time I was thinking: I have a stack that could have prevented this. I have a system that could give her remote support without me being chained to a terminal at 2am every time something goes sideways.
So we started building.
Project Mom Shield. Phased deployment so nothing about how she uses her computer changes overnight.
Phase 1 is in. Five-minute job on the last visit. Changed her router DNS to AdGuard's family servers. Public infrastructure, no equipment, no apps to learn. She doesn't know it's there. She just notices that the ads got quieter and the scam sites stopped loading.
Phase 2 is in production. Pi for her house running AdGuard Home locally, Tailscale joining the mesh, RustDesk so I can remote in when she needs help. The architecture is already proven... I tested the relay on the visit, laptop on her couch, full reach back to my home office one state away. First try. No third party. No "share this code with the support agent." My mesh. My pipe. My control. The Pi just makes it permanent.
Phase 3 is monitoring once Phase 2 is in. CrowdSec on the Pi, log forwarding to my InfluxDB, her network health on my Grafana dashboards. I'll know about her problems before she does.
Here's what I want you to notice about all of that.
The visit happened.
The visit happened because there was time for it to happen.
The 55-container stack didn't chain me to Tulsa. It was the foundation that made the trip possible. The work didn't get smaller. The work got delegatable. And once it was delegatable, the operator could leave.
That's the whole point of the model.
I have a garden now.
I've never had a garden in my life. Killed every plant within reach for forty-something years. These accursed black thumbs, that's how I always described it. Wasn't an exaggeration.
The garden is thriving. Things growing. Things staying alive. The whole thing is on a schedule I actually keep because there's space in the day to keep it.
I'm not going to overwrite this. It's a garden. It's not a metaphor.
It's just that three months ago I would have killed it the way I killed the last six gardens I never quite started.
The difference isn't that I learned to garden.
The difference is that I had time.
Doug is a dog.
He's a Shih Tzu, he's a good boy. He found me, showed up at my door 2 weeks ago like we were long lost buddies and hasn't left my side since... BUT A dog needs walks. A dog needs attention. A dog needs presence. None of that fits in a 14-hour terminal day. None of that fits in an "always on call" rhythm.
Doug exists because the rhythm changed.
I'm not going to overwrite this one either. He's a dog. He's a good dog. He's asleep on the floor right now and he'll have opinions about it when he wakes up.
The fact that I get to be here for that... that's not a small thing.
That's the thing.
Most tech promises you time and gives you the opposite.
Every SaaS subscription was supposed to free you up. You ended up with twelve dashboards, twelve invoices, twelve logins, and twelve places where your data lives that you don't control. The work didn't get smaller. The administration of the work got bigger.
Every AI tool was supposed to automate the boring parts. Most people end up babysitting their AI more than they used to do the boring parts themselves. Prompt engineering became a job. Reviewing AI output became a job. Cleaning up after the AI's confident hallucinations became a job.
The pattern is the same. The tech absorbs more of the day, not less. The operator becomes the maintenance layer for the tools that were supposed to maintain themselves.
MPDC is built to be different.
The stack is real. Fifty-Five containers and growing. Full security operations center. Self-hosted everything. The kind of infrastructure that, in a normal architecture, would consume the operator entirely. There would be no Doug. There would be no garden. There would be no drive to NWA.
The reason it doesn't consume me is governance. The 70/30 model isn't a slogan. It's a working contract between me and six AI stations who handle the 70 that used to be my whole day. One does the infrastructure work. Another does the content drafts. A third does the legal and business research. I have a bot that handles community engagement scaffolding. One that does the intelligence sweeps. And finally I have the bridge coordinates them all.
I do the 30% that AI can't and/or shouldn't do.
I make the call. I take the risk. I write the voice. I sit in the chair when the chair needs sitting in.
And when the work is done... the work is done.
There's a chair to sit in.
A dog to walk.
A garden to water.
A drive to make.
The point was never more tech. The point was getting your life back.
That's the whole point.
If you're reading this and you're one of the Jolt and Bawls crowd, you already know what I'm talking about. You built the homelab to escape something. Most of you got buried under the thing you built to escape with.
The way out isn't more tech. It's better governance. It's delegation that actually delegates. It's letting the machine do what the machine is good at so you can do what only you can do.
Which is, you know, live.
The trilogy explained how to govern AI without getting burned. This article is about what the governance is for. It's not for safety. Safety is the floor. It's for life. Life is the point.
Doug just woke up. He's standing by the door. He has opinions.
I'll see you next time.
Cheers, ~Chris
Discussion in the ATmosphere