We write about the operating decisions that don't usually get written down — how a small team decides what needs sign-off, what an audit trail should actually contain, and what changes when you hand a function off from an AI-assisted process to a human hire. Most of what's here comes directly from running Orlog AI on Orlog OS.
-
Eight hours unreachable, reported healthy the whole time
An outage no dashboard could see, an audit that found the same defect nineteen more times, and the loop conductor's first real autonomous cycles.
-
Three containment controls were down and nothing noticed
An integrity gate disarmed by a lost file mode, two more controls found down the same night, and the replacement gate we built to hold the weight.
-
We ordered a credential rotation, recorded it as handled, and never ran it
A rotation that existed only on paper, three confident theories that were wrong, a build red on purpose, and a capacity fix we were told we could not buy.
-
Three of our production binaries had no source in git
Live programs built from uncommitted candidates, a 2,041-file pull request that earned an ultimatum, and two sessions that were right to stop.
-
We made the same deployment mistake twice in four days
Four autonomous drives in seven days, two self-inflicted outages from one missed step, and four systems that reported success they had not earned.
-
The six-day soak lasted 89 minutes and we had already seen why
We moved five personas into isolated containers, started a six-day soak, and ended it the same night on evidence we had written off an hour earlier.
-
We added eleven personas to a dispatch pipeline that had been dead for four days
The busiest week in our record, and the live-fire proof that the new team worked has the bug that broke it sitting in its own transcript.
-
The untested claim was the load-bearing one
Autonomous multi-hop dispatch finally worked, on the one fix nobody had tested; the same week we leaked a password and wrote the wrong prevention.
-
The autonomous loop went live and could never have worked
Four separate green checks turned out to be proving nothing, and the week we found that out is the week our testing standard changed.
Follow the work
Articles publish as we run the operating loop. The fastest way to hear when new posts land is to be on the early-access list.
Request early access