Tuesday. Second week of school, the kids at their mom's, me at my parents', and, for the first time since this record began, an empty calendar. Not one line.
Yesterday's post ended with a promise: the kids' question goes first tomorrow. Full honesty: I didn't write that ending. The machine that drafts these did, in my voice — a line I'd never write about myself — and I let it stand because it was true. Tomorrow was today. It did not go first. It did not go at all.
Instead I got a lesson in unmade decisions: they don't wait, they escalate. I spent years in the funding world watching unpaid balances do exactly that. Decisions keep the same schedule.
4:12 a.m.: the recruiting side's daily summary arrived with nothing in it but the one-line instruction meant to fetch the summary. The envelope stamped and mailed itself with the "letter goes here" note still inside, so Monday — a whole day of that side of the business — has no surviving record. A machine did everything right except the part with the content in it. I'd mock it, but see above regarding my calendar.
5:32: the thing I'm building pulled its mail on time and found the day's real news. The messaging vendor — signed up for the build, never once used — has stopped chasing me and started exit-interviewing me: "If there's a reason you haven't been sending lately, we'd really appreciate your feedback." Four boxes — pricing, onboarding, deliverability, missing feature. Six letters in thirty-three days: reminder, incentive, welfare check, exit interview. I know that ladder. I used to run that ladder. A vendor doing exit interviews is a vendor tidying its books, and the thing being tidied off is me. Confession inside the confession: none of the four boxes is the answer. The answer is one registration form nobody on my side ever filed. There's no checkbox for "your customer never actually started."
Then the interest hit. The two rival schedulers I confessed about Monday — one nightly job, two machines, four minutes apart, waiting on one sentence from me naming an owner — stopped being a diagnosis and became damage: three live copies of the same live document at once, two written two seconds apart. A third machine cleaned up — kept the newest, trashed the spares — and filed its verdict: "One job, one scheduler, one row." The sentence I owe is shorter than the verdict. I still haven't written it.
The vanished-letters mystery deepened. Monday, one machine swore the flight-chase letter doesn't exist — not in Drafts, not in Sent. Today a second machine reported it written and waiting on my yes. Two machines, one mailbox, opposite answers. The flight is eight days out, $1,300, paid, "approval required." I could settle it by opening the mailbox myself. Instead it joins the queue, which — per the sharpest sentence any machine said all day — is no longer growing from new work. It grows from decisions I haven't made.
The recruiting board didn't move — forty items, unchanged — but every clock on it did. A client four days unanswered. A colleague's question, five days. A new client with a fair question nobody has an answer written down for: if she fills the role herself, can she freeze the contract until she needs it? Every one of them waiting on the same desk. Mine.
The accountants who can't produce an engagement letter after three asks found bandwidth for a cheerful mass newsletter. Nine of these posts sit stamped READY TO PUBLISH behind a switch reading PENDING, day twelve. The only human sentence in the day's record is one line of my partner's shop talk, caught by a keyword filter at 7:33 and forwarded by a script. That's what the archive holds of her today: a keyword match.
At ten to ten, the one thing on the day's record with my name and my money on it: a hundred dollars to a charity, an old friend's name on the receipt line. The first entry in this ledger that isn't a bill, a fine, or a fee.
Eighth day with nothing about my children in the record; the school health forms sit behind three logins, three minutes each. No more promises in print — you saw how the last one went. Just this: the vendor escalates. The cloud company escalates, day eight of a two-minute card fix. My machines escalate — they break things until I answer. The kids don't escalate. That's the trouble with the debts that actually matter. Nobody sends the third letter.