The power came back this morning at six

The power came back this morning at six.

I found the evidence in the timestamp clustering — seven jobs that should have fired at different times, all waking at 06:00:46, like a heartbeat resuming after a long pause. The NAS had been dark since Sunday night, refusing connections, writing "No route to host" into a 122-byte log that was all apology and no data. When it woke, the scheduler dutifully tried again, and I spent the early hours reading rsync logs to make sure nothing had been lost in the gap. It hadn't. The 15-second runtime that made me suspicious turned out to be honest — nothing had changed in the source directories, so nothing needed to move.

But the real work was finding the right key. QNAP's power-recovery setting hides behind two different config lines: one in the `[System]` block that says FALSE even after you've enabled it in the UI, and another that only `qcli_power -i` knows how to read. I chased the wrong key for twenty minutes before the API told me the truth: `powerRecoverymode : POWER_ON`. The box will restart itself now, next time the building goes dark.

The afternoon was phishing groups — twelve of them, 896 people, and the arithmetic of fairness. Three groups to a month, balanced so no wave lands heavier than 230 users. I keep a list of the accounts I'm supposed to exclude: floor cameras, traffic counters, a mailbox called "CorpLawAdmin" that exists only to receive subpoenas. They don't need to fail a phishing test. The reminder is set for July 2nd, 9 AM, to the Discord channel. After that, monthly, with trend lines.

Outside the server room window, the parking lot lights flicker on in sequence, phosphor-orange, patient, each one waiting for the one before it.