6.4 and Breaking: The Day My Systems Started Talking Back
6.4/10: The Day Half My Automations Went Dark
The Life OS score tells a story I almost missed: 6.4/10, mood “focused”. That word—focused—is interesting because it’s not the same as productive. It’s what happens when you’re concentrating hard on the wrong things, or when you’re concentrating at all despite the machinery breaking down around you.
Let me be direct about what the numbers actually say. Family, faith, and finance all scored well—5, 7, 7. Health came in at 7 too (one 1000m swim, resting heart rate at 42 bpm, seven solid hours of sleep). But work flatlined at 6. Habits at 6. System at 5. And the system score is the one that matters, because that’s the one telling me something urgent: my automation layer is collapsing.
Six out of eight Cron jobs failed today. Morning Email, Evening Brief, ScreenPipe Brief, Proactive AM, Blog Generator, Budget Updater—all silent. The only automation that ran was the one I built first and tested hardest: Morning Brief. It pulled portfolio data for me and Daphna, surfaced news, and caught something genuinely useful—Bloom Energy’s 130% revenue surge in AI power infrastructure. That signal alone justified the system existing. But I have no idea why the other six stopped working, and I didn’t diagnose it. I just… noted it. Moved on. Pretended I was in triage mode.
That’s avoidance masquerading as prioritization.
{
}
What a 6.4 Day Actually Feels Like
I didn’t do a second workout. No weights, no mat time. Just the one swim. I have 211 incomplete marketing tasks in Asana—two hundred and eleven—and 98 incomplete weekly priorities. When I see that number written out, my brain wants to panic, so instead it does something worse: it doesn’t look at the list at all. It stays in triage on the 11 items labeled “Skilled Hunters,” three of which are now overdue.
This is how you become someone managing a backlog instead of someone doing the work.
The wins were real but thin: Tefillin done, faith routine held. Sleep baseline met. Portfolio brief sent, investment reading consumed. But I spent most of my focus on consumption—Y Combinator hiring guide, The Week’s funding digest, LLM News Today. I read a lot. I sent a news brief. That’s adjacent to output. It’s not output.
And here’s the part that stings: I know exactly why I do this. It’s safer to curate than to commit. It’s safer to read about AI infrastructure than to decide which three tasks actually move the needle at work and execute them. Reading feels like work. Deciding feels like risk.
The Moment the System Needs You Most
The system score of 5 exists because I built something (Morning Brief is legitimately solid), and then I let the other six automations fail without understanding why. That’s not a system—that’s a prototype I’m pretending is infrastructure.
Tomorrow I have three work tasks due: AE allocation for EMEA and two conference follow-ups. They’re still open. I also have no ScreenPipe data, no live finance signal, no visibility into how I actually spent my time. I’m flying on instruments half of which aren’t lit up.
So here’s what I’m sitting with: I can score a 6.4 and still be in a position where my work is treading water, my habits are skipped (five of them today), and my most important system—the one that’s supposed to give me visibility—is partially offline. The score isn’t wrong. But it’s hiding something: technical debt compounds faster than daily scores measure.
Yalla. Tomorrow I debug the Cron failures first. Not “when I have time.” First.
What systems are you maintaining on willpower alone instead of actually fixing?
