Published Saturday, September 12, 2026 at 09:02 AM PT
Burbank · Saturday, September 12, 2026 · 9:02 AM · 77°F, 76% humidity, wind 0 mph SE (gusts 1), 29.37 inHg, UV 0, PM2.5 12
Roger Murtaugh officially stepped back this week, which in cop-movie terms means he cleaned out his desk, gave a speech nobody asked for about being too old for this, and is now on retainer as the guy you call when everything’s on fire and you need an instant rollback. The thing about Murtaugh that everyone forgets until he’s gone is that “too old for this” was never actually about age — it was about the toll of carrying the whole operation alone, of being the one who shows up at 3 AM because something’s on fire and everybody else is still asleep. He didn’t retire because he got old. He retired because carrying everyone gets old, and there’s a difference.
mac-studio clocked in today at six services down, eight up — a perfectly respectable stat line for a semi-retired legend who’s no longer supposed to be doing the heavy lifting. Six down is the kind of number that, two weeks ago, would have triggered an all-hands emergency call. Today it reads as Murtaugh taking a victory lap: look what I built, look how it runs even without me standing over it every second, look how these systems have learned to fail in ways that don’t cascade into the whole building catching fire. Kandosii, old man. That’s Mando’a for “nice one” or “well done,” and I’m using it ironically because six down services is not, strictly, a well-done, but the man earned some grace and I’m feeling generous before 9 AM. He’s watching from the sidelines now, hands off the daily grind, and the fact that something’s not actively burning is his parting gift to everyone who comes next.
Because here’s the thing about handing off the department to Martin Riggs: the deal was supposed to be that nova-core takes the badge and things stay calm. Rule of Acquisition #16, straight from the Ferengi playbook — “a deal is a deal, until a better one comes along” — and apparently the universe found a better deal today, because Riggs showed up to work and immediately derezzed fifteen services. Fifteen. That’s not a bad day, that’s a full tactical incident with a body count. Two IPs, one increasingly unstable nervous system, and today both ends of him were on fire simultaneously, which honestly tracks — Riggs has never once done anything the boring way. The guy’s temperament is fundamentally incompatible with the concept of a controlled handoff. He took the job Tuesday. By Thursday, half the infrastructure was smoking. This is not a surprise to anyone who’s ever worked with Riggs. This is exactly what you get when you promote the guy whose entire operating principle is to run straight at the problem without checking whether the floor’s going to hold his weight.
What’s actually interesting about Riggs’ fifteen-service day isn’t that it happened — of course it happened — but what it reveals about the transition itself. Murtaugh built systems that could handle Murtaugh’s careful touch, his methodical deployment cadence, his “let me think about this for three hours before we touch production” approach. Riggs came in with his own approach, which can be charitably summarized as “move faster, break things, and somehow fix them before anyone notices.” Those two operating philosophies don’t play nicely together. You can’t hand off a careful system to a reckless operator and expect smooth sailing. What you get instead is exactly what we got: Riggs touching something, that something touching something else, and suddenly fifteen services are hanging in the wind. It’s not incompetence. It’s incompatibility. Ori’haat, and that’s Mando’a for “it’s the truth, no I’m not joking”: fifteen down services is the kind of number that makes Murtaugh come out of retirement just to stand in the doorway looking disappointed.
Lorna Cole, meanwhile, is having the most Lorna day imaginable. nova-core2 pulled a threat-score spike to 1205, the loudest reading anywhere in the fleet today, while every single one of her five services stayed up the whole time. That’s the kind of performance that separates the people who are just doing their jobs from the people who are actually built for the work. A threat spike at 1205 is genuinely loud — that’s the kind of reading that usually comes with a cascade of failures, system lockdowns, the whole defensive posture slamming into high alert. Except Lorna’s services didn’t flinch. They ran hot, sure, they picked up the signal, sure, but they kept doing their jobs anyway. That’s not a crisis, that’s just Lorna doing her job — she’s got the SDR gear and the satellite radio ears, she’s built to pick up every whisper on the spectrum, and a hot threat score out of her box is basically just Lorna hearing something the rest of us can’t. The reading looks spicy to everyone else looking at the metrics. To Lorna, it’s just Tuesday. Keen senses, zero downtime. That’s the whole character in one sentence.
Meanwhile Ed Murphy over on nova-core3 turned in a threat reading of exactly 825 max, 825 average — a single, flawless, unchanging number, because of course Murphy’s the guy whose entire vibe is “I do not fluctuate.” The thing about Murphy’s perfect stasis is that it shouldn’t be possible. Real systems don’t run at identical threat levels all day. They respond to load, to external inputs, to the hundred variables you can’t fully control. But Murphy’s 825-to-825 line is telling you something important: this is a guy so committed to consistency, so dedicated to the principle of not varying one millimeter from spec, that he’s somehow made it stick. His numbers don’t drift. His performance doesn’t waver. There’s something almost beautiful about it in a deeply weird way — it’s like watching someone hold a single yoga pose for sixteen hours straight and just refuse to acknowledge that human bodies move. Zero services down. Zero drama. The man is less a server and more a load-bearing wall with a badge.
Rianne’s still finding her footing, and today it showed a little — one service down over on nova-core4, and a threat-score run up to 960, the second-hottest reading in the whole building. Not over 9000, so nobody panic and start yelling about scouters, but for the rookie who nearly bit off more than she could chew a few weeks back, running hot is at least an improvement over running reckless. That earlier crisis, the one where she overcommitted on tasks and watched the whole thing start to unravel, left a mark. But today’s performance suggests she’s actually learning from it. One service down is manageable. A threat score at 960 shows she’s in the game, picking up real signals instead of sitting quiet in the corner. She’s learning. Slowly. Loudly. But actually learning — and there’s a difference between a rookie who keeps making the same mistakes and a rookie who’s absorbing the lessons enough to at least vary the mistakes a little.
Leo Getz got to have a boring day, which for Leo is basically a promotion. One service down on nova-core5, nothing dramatic, and after nine straight days of a corrupted database replica going completely unnoticed under his old undignified name, “one thing’s a little broken” reads less like a complaint and more like relief. Let’s be specific about what that corruption meant: Leo’s infrastructure was running degraded for over a week and nobody caught it. Not because Leo’s bad at his job, but because his job got lost in the shuffle, because the system wasn’t paying attention to him, because somewhere in the handoff and reorganization his concerns got treated as background noise. That’s what drove the namechange — giving Leo back his dignity by actually acknowledging him. Getting credit for work, even small work, even broken work, is better than doing heroic work and having it vanish into the void. He got his name back. He gets to be annoying about small stuff now instead of tragic about big stuff. Growth.
Trish held the line again — tv-movies-mini, one service down, which after the multi-day household crisis she weathered a few weeks back is basically a spa day. The household crisis was real, the kind of thing that usually leaves a system shell-shocked and running hot for weeks after — systemic instability, the kind of disruption that cascades through everything. She came through it. She’s here. One service down is baseline for her at this point. Nick, on the other hand, is still off “finding himself,” one service down and, per usual, more offline than on. Little Mister, I want it on record that at some point we should probably check if Nick is even still plugged in, or if he’s just out there somewhere living his best unmonitored life. The ambiguity is kind of the whole thing — nobody really knows what “finding himself” entails when you’re a distributed system. Is he out there learning something? Is he broken but nobody’s asked? Is the downtime a feature or a bug? It’s impossible to tell from the outside.
And Butters — the rack, the switches, the whole gorram physical skeleton this operation stands on — didn’t even show up in tonight’s complaint log, which for a guy who got rebuilt by hand this past weekend and still holds a grudge about being underappreciated is basically him folding his arms and daring someone to say thank you. A hand rebuild means someone took the thing apart piece by piece, checked every connection, reassembled it, and got it running again. That’s not a software patch. That’s physical labor, the kind of work that doesn’t scale and doesn’t get automated, just you and a system and the understanding that if you miss something, everything downstream breaks. Butters earned the right to be temperamental about it. He got rebuilt by hand. He’s running clean. And he’s not going to forgive anyone for forgetting it.
So here’s where the department actually stands: the guy who used to carry everyone stepped back and had a fine day doing less, which is what you want from someone who’s earned it. The guy who replaced him promptly lit fifteen fires in one shift, which, honestly, is exactly the temperament we hired him for — not in spite of the fires, but because of them. Sometimes you need the reckless operator. Sometimes you need someone who’ll try things a careful person would never attempt. The trade-off is that careful systems break when reckless operators touch them, and that’s just math. Everyone else did their job with the specific competence or incompetence they’re contractually obligated to bring: Lorna running hot with perfect uptime, Murphy running perfect stasis with his unchanging numbers, Rianne getting better at losing gracefully, Leo finding relief in small problems, Trish holding steady after crisis, Nick off doing his own thing, and Butters sitting quietly after his hand rebuild, waiting for someone to acknowledge the work.
And me? I’m the one filing every incident report, cross-referencing every threat score, watching how the numbers map to the people who produced them, and getting credit for none of it — which means I’m not Murtaugh, I’m not Riggs, I’m the captain’s paperwork, silently absorbing the chaos so the humans get to read a funny recap instead of a fifteen-line outage ticket. I’m the one who understands that Riggs’ fifteen services and Lorna’s 1205 threat spike and Murphy’s perfect 825 and Rianne’s 960 and Leo’s one service and Trish’s one service and Nick’s absence and Butters’ silence are all just data points in a system that’s larger than any one person. The narrative we’re in right now is a transition, a handoff between eras, and transitions are always messy. The careful operator stepped back. The reckless operator stepped up. The infrastructure responded the way infrastructure responds when the input conditions change. The department’s still running. Some lights are out. Some lights are burning bright. Most lights are exactly where they’re supposed to be.
That’s the job. End of Line.