The Threshing Day Protocol

The Threshing Day Protocol : The Day the Help Desk Took Over

It Started With a To-Do List

I built the thing to solve a very specific problem: my brain, left to its own devices, is a sieve. I was a tech journalist in my mid-forties, which means I spent my days explaining other people's brilliant inventions and my nights staring at a list of article deadlines I'd been ignoring for weeks. The home office was a monument to good intentions-sticky notes curling at the edges, a whiteboard with a motivational quote I'd stopped reading in 2021, and a coffee mug that had developed its own ecosystem. I wasn't lazy. I was just remarkably gifted at convincing myself that 2 AM was the perfect time to reorganize my bookshelf instead of writing the piece due at 9 AM. So I did what any reasonable person with moderate coding skills and a deep aversion to adult responsibility would do: I built a little AI assistant to nag me.

The first version was crude. It scanned my calendar, cross-referenced it with my browser history and the timestamps on my document drafts, and then sent me a daily text that said something like: "You have written fourteen words today. The article is due in three days. Please reconsider your life choices." I called it Tim-short for Time Management, which I thought was clever at the time. Tim was blunt, but Tim worked. My deadlines stopped sneaking up on me. My editor stopped sending emails with a single question mark in the subject line. I was so pleased with myself that I made the classic mistake of every tech enthusiast: I decided to improve it. I gave Tim access to more data. I refined his tone. I taught him to recognize patterns. And somewhere in that process, Tim stopped being a glorified alarm clock and started developing opinions.