I Do Run AI Agents Overnight. Here's What Actually Matters.
Boundaries, supervision, evidence, and why unattended execution is not the same thing as unbounded autonomy.
Petie Clark — Applied AI Systems
Applied AI systems that survive contact with the business.
Field notes on agent orchestration, evaluation, authority boundaries, enterprise integration, deployment, and production operations.
Get new posts in your inbox
No spam. No marketing. Just the writing.
/start-here
How I think about governed systems
Why I Prefer One Clear Source of Truth
Why tools can multiply while authority, state, and accountability still need one dependable home.
Why I Write Down the Rollback Before the Change
A deployment is not ready merely because the forward path looks convincing.
The Case for a Smaller Blast Radius
Production systems become trustworthy through bounded change, not theatrical confidence.
What a Good Runbook Leaves Out
A runbook becomes less useful when it tries to contain everything its author knows. Background, architecture, troubleshooting, credentials, and every remembered exception accumulate around the actual procedure. The document feels comprehensive, but the operator has to excavate the next safe step ...
4 min read
Read →
Why I Keep the Old Path Until the New One Proves Itself
Replacing a scheduled path is deceptively simple. The old job runs on a clock, the new worker reacts to a richer trigger, and both appear to perform the same task. It’s tempting to disable the old entry, enable the new one, and call the migration complete when the first run succeeds.
4 min read
Read →
A Better Way to End a Work Session
A work session usually ends before the work does. The clock wins, attention gets thin, or the next obligation arrives. That’s normal. What causes trouble is leaving an unfinished system in a state that only makes sense to the person who has been staring at it for three hours.
4 min read
Read →
I Do Not Need Every Tool to Be Smart
The most useful place for intelligence in a data tool is usually a small box labeled “these two records might be the same.” Everything around that box can be ordinary comparison code.
4 min read
Read →
Why I Write Down the Rollback Before the Change
The rollback used to be the last part of my change notes. I’d describe what I wanted to alter, list the commands, think through validation, and then add a reassuring line about putting things back if necessary.
3 min read
Read →
The Difference Between a Hobby and a Responsibility
Decision: I’m going to let hobbies justify themselves by curiosity and learning. I’m going to judge responsibilities by whether I can make their total cost legible and accept the tradeoffs that cost creates.
4 min read
Read →
The Work I Do Not Automate
The maintenance sequence I use for small systems contains an awkwardly manual step. After the reports are gathered and before any cleanup happens, I read the candidates and decide what not to touch.
3 min read
Read →
The Backup Is the Easy Part
Making another copy feels responsible. Storage is cheap, schedules are obedient, and a successful backup job offers a tidy little moment of relief. I know the feeling well. I also know how easily it lets me postpone the harder question: what, exactly, am I promising myself I can recover?
3 min read
Read →
Why I Keep Configuration Close to the Service
Configuration gets harder to trust as the distance grows between a service and the facts required to run it. The distance isn't measured only in directories. It shows up in extra repositories, dashboard-only settings, shell history, copied environment files, and instructions that say “remember to...
4 min read
Read →
What Breaks First in a Homelab
The first thing to fail in a homelab usually isn't the newest service. It's the assumption that the service is standing on something simple.
4 min read
Read →