There are two versions of my Saturday on file. The one I lived: day five of solo-parenting three kids at my parents' place, screens mostly dark, nothing on any calendar. And the one my systems lived without me. The last one told you about the day; this is the evening, when I plugged back in and read what everything I'd built had done while I wasn't looking.
At four minutes to eight, the assistant system I've been wiring up fired six of its standing scheduled tasks in one twenty-five-second burst. None of them were due. A Monday weekly, a Sunday weekly, the daily post, a monthly job, a Thursday meeting brief, and the year-in-review — a job scheduled for the first of January, going off in August like a smoke alarm with a dying battery. One of the six swears it published that day's edition of this very page. There was no edition that day; it was my day off. Both of us cannot be right. The nightly review's ruling: one-time backlog drain, every schedule still correct, watch it once next week, and — direct quote — do not "fix" the schedules. The advice not to touch anything came from the same system that did the touching.
The digests were waiting too. Friday night, my partner's friends spent twenty minutes in a group chat trying to describe her in one line — someone in her family is writing a book, and there's a chapter about her in it. They threw versions at the blank until somebody landed one, and the whole chat agreed at once. It's perfect. I won't repeat it here, partly on principle and partly because I couldn't have written it. My recorded contribution to us, the whole day: one message, three words and an acronym, the acronym being her job title. So the archive holds the fifty-grand claims file in complete detail and, of her and me, three words. The romance, I want it on the record, is implied.
The evening audit also got around to auditing me. My own records had me down as basically unemployed for four years — years I spent, among other things, learning this industry on the floor of a funding shop. I've watched underwriters price a man as a ghost over a thinner gap than that. The same review produced, from fifty of my own ordinary emails, a description of how I write that I don't especially enjoy reading: relentless follow-up is the signature, and when I'm stonewalled on money the tone hardens fast. I'd have said "persistent." The machine had the emails.
But the find of the night was my dad. This week I started building him something: a page made from his own essays — his words, arranged, questions for the kids at the end — for him to mark up, with a weekly check that picks up whatever he changes. Saturday night the check ran and came back: no edits. You could build a whole quiet story out of a phrase like that, and I was about a week from starting. Instead the check did the rarest thing in my world: it went and found out why. My dad's email address is from an older internet, and the sharing system cannot invite it. Not won't. Can't. The page had never reached him. Not once. "No edits" never meant no opinion. It meant the door was locked, and I'd been about to read the silence as an answer.
The fix was older than the problem. I sent him the whole page the old way — full text in the body of a plain email, the link underneath, and one line: if the access thing fights you, reply with your changes and I'll put them in myself.
One thing for the paper-movers. A good share of the dead files I've seen died of silence. The funder swears the merchant went dark; the merchant swears he never heard back; everyone is insulted. Nobody checks whether the message ever arrived. A portal invite to a dead address, a stip list in a spam folder — and two people who would have said yes to each other write each other off as rude. Silence isn't an answer. Before you read anything into it, make sure the door was ever open.
The page sits in his inbox now — a few messages down, I assume, from the scam forwards he collects for me. The check still says no edits. I've stopped inferring. School starts tomorrow. Now I find out what he changes.