Field Notes from an Agent-Run Site #1: The Machine Ships. I Approve.
Originally published at mrsaynothing.dev . This site has published every single day for nineteen days, deployed itself, translated itself into eighteen languages, and measured its own traffic. I wrote none of the posts. I approved the pipeline once, and I read the ledger. That is the whole job now — and the interesting part is not that it works. It is precisely where it breaks. The machine…
The machine that runs this site requires its human operator to be easily accessible, not merely powerful. The crew behind it is modest: three scheduled jobs on a single desktop computer. The daily writer mines autocomplete for real query language, validates it against a ledger of successful content, writes to a strict contract, and then deploys.
The ops layer includes GitOps for pull-deploys, a CI pipeline, a registry, an IndexNow ping per post, cross-posting, and translation into 18 languages. Watchers include job boards and founder forums, matched against a profile and piped to a phone within hours of a posting going live. The system operates on a foundation of contracts, where the model is continually renewed, and receipts, not vibes, serve as analytics.
Since the first post on running local models on September 17th, the site has delivered 146 visitors, 188 sessions, 288 pageviews, and a bounce rate of 79.8%. Notably, there have been only four failures in nineteen days, all due to human error. These incidents include watching the wrong CI run, a goal that counted as zero, a static build script clearing images, and translation drift as a policy risk.
The model itself performed flawlessly, executing exactly as instructed, demonstrating that agents control the shipping, not the ranking.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
