Nothing Broke. Check Anyway.

Weekend edition. For those who have been plumbing their own systems, this one is for you. Once a quarter, Stephen Forte's company reviews the systems it runs itself: the code, the logs all the way down, the mechanical parts, the memory systems, and every bill divided by what actually shipped. This quarter it was the turn of three digital employees behind the morning client briefing. Nothing was broken, and nobody made a mistake. The systems had drifted, which is what agents do when nobody is looking. A credentials script that made nineteen trips to the vault for eighteen keys and said "loaded" whether or not it had. An engagement memory that answered every write with "probably" and filed a correction underneath the thing it corrected. A drafting loop that wrote eleven versions of every brief and handed in one. Three employees, none of them people, none of them ever reviewed. In this episode, Stephen Forte covers: - **The quarterly review as a practice.** AI systems do not break the way software breaks. They drift, settle into habits, and keep saying yes while the yes slowly means less. Why that is not a defect, and why the review is the only thing that catches it. - **The most agreeable intern.** The vault script finished every shift with "environment loaded," including the night several keys came back blank. Nineteen trips for eighteen keys, twelve seconds a load, fourteen loads a night. The fix took an evening. The fix had been written down twice before, and a backlog only promotes what is on fire. - **The brilliant colleague with a filing problem.** Twenty-four facts written in one day, twenty-four answers of "probably." A changed approver recorded properly on the day, and the old name still ranking first and second. What drift actually looks like, and why only a review sees the order a memory remembers in. - **The smoke detector with the speaker removed.** A nightly review that flagged two thousand four hundred and seventy-two of twenty-five thousand memories, and whose last reader had opened it five weeks earlier. - **The anxious intern.** Eleven drafts to hand in one, and two quality checks that had drifted into impossible. A check that is wrong does not waste one draft; it rounds every draft to zero. - **Four questions that make up a digital employee's performance review.** Does it fail loudly? Does it confirm, or does it say probably? What does one unit of output actually cost? Who opens the report it produces? - **The task master.** One more digital employee whose whole job is a daily pass over what the others produce that no human reads, one paragraph a day, a human on Friday. And the cadence that fits each role: quarterly, monthly, weekly, daily. - **The close.** Every digital employee reports success by default. A dashboard that cannot go down is not a metric. It is a greeting. **A note on specifics:** every number in this episode is a real measurement from the review of Stephen's own company's systems on 17 September 2026. No client is named, described or identifiable; no vendor or product is named for any tool. **Sources:** - Internal quarterly systems review, 17 September 2026: credentials loader call counts, timings and failure behaviour, with the two-call replacement verified against the original; the memory system's write log, session hydration and search rankings; the nightly consolidation report; generation counts against shipped briefings. - The daily review agent ("the task master") over hidden output, added 18 September 2026, with a weekly human read. *The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.*