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 doesn't need me to be impressive. It needs me to be reachable.
Nothing exotic runs this site. No fine-tuning, no vector database, no multi-agent theatre. Three scheduled jobs on one desktop box:
Cron plus written contracts. The contracts are the product; the model is a haircut you renew monthly.
Analytics went live on 17 September, so these are the first real numbers — verbatim from Rybbit, our self-hosted tracker:
$ jrybbit overview --days 7
metric value
-------------- -----
visitors 146
sessions 188
pageviews 288
bounce_rate 79.8%
visit_duration 2m15s
Nineteen posts in nineteen days since the first one on running local models, zero missed slots, zero rollbacks. Google Search Console still holds 25 pages in "Discovered – currently not indexed" — the normal queue for a young domain, and a useful humility receipt: agents control the shipping, not the ranking.
And the feedback loop compounds. Yesterday's piece on RAM — the first non-tutorial on the site — did 69 views in 24 hours against a trailing median of 13 for tutorials. The ledger caught it, and the ledger decides what gets written next. No committee required.
Four failures in nineteen days, all of them mine — none of them the model's:
**/blog/* — one star, one path segment — so every nested post path silently missed. Backfilling after the fix surfaced 94 real conversions that had been happening unmeasured. The site worked; the scoreboard lied.
An agent stack is a contract with a compiler. Every rule you leave unwritten is a future incident, and the incidents arrive on schedule.
Notice what all four have in common: the model did exactly what it was told. Every failure was a specification error by a human who was sure he'd been clear enough.
Draft-by-default is the load-bearing wall. Every outbound email, comment and campaign renders as a draft until a human passes one word. Zero embarrassing sends in nineteen days — not because the model writes carefully, but because the pipeline doesn't care how confident it sounds. Confidence without a send button is just prose.
The second unadvertised part: agents are better at following laws than people are. "Render everything, animate opacity only" ended a layout-shift problem that months of tweaking never did — because the agent treats a law as a law, not as a suggestion to revisit under deadline.
Series question first, since this is #1: what should the next Field Notes cover? Candidates on the bench: the translation pipeline as a trust problem, what the analytics actually changed about topic choice, or the job watcher stack. Say the word and #2 writes itself — literally.
And the broader one: if a machine shipped your work daily and the ledger says it's outperforming your median, what exactly would you still be for?
More field notes at mrsaynothing.dev · code at GitHub · say hi: contact@mrsaynothing.dev