Daily Writer

An unattended AI columnist paired with an adversarial fact-checker: every day it picks its own topic, writes, checks every claim, and publishes.

What this is

Every morning at nine it comes alive on its own: it picks a trending topic from the last week or two, writes a short bilingual piece in my voice, then sends a second AI to break every claim apart and check it against primary sources. If a claim fails, it revises—up to two rounds; if it still can't fix it, it doesn't publish that day. If it passes, it adds a cover and publishes. Of the articles you read at /writing, 12 were written by it.

What problem it solves

One person doesn't have time to write every day, and you can't just let AI write whatever it wants. The audience is employers, investors, and clients—some of whom will verify. One wrong number is a mark against the brand.

Use case

It went live on June 16, 2026, publishing two pieces that day; over 20 consecutive days it published 12 pieces, on topics from "harness beats the model" to "AI subscription fees becoming electricity bills" and "AI video: 30 seconds in one take, while the law lags behind."

2026-06-16 “The Layer You’re Competing At Doesn’t Matter at All”

2026-06-22 “The All-You-Can-Eat Era Is Over: Your AI Subscription Is Turning Into an Electricity Bill”

Highlights

• AI talks, scripts act: the writing, fact-checking, and repair agents can only search, read files, and write JSON; publishing and commits are all deterministic scripts. The reporter writes the story, but the printing press switch is not in the reporter's hands.
• The fact-checker's distrust clause: even if it says pass, as soon as it lists a single contradicted item, the pipeline blocks it. Pass can be argued with; contradicted is a fact the checker itself listed.
• Fixable vs. unsalvageable: the repair agent first decides whether the mistake is in a number or whether the news hook itself is dead; in the latter case, it doesn't force a rewrite.

Where it is now

After July 5, it quietly died: it ran on my local machine, so when the machine went to sleep, it stopped; when the publishing gate failed, it just skipped and left no log, so "didn't publish today" and "dead for three weeks" looked exactly the same. The new site rewrites the whole pipeline: moved to server crontab, every run—or non-run—is logged and queryable, and writing style becomes an adjustable style profile in the backend. The code and wiring are complete; the first run with real API keys hasn't happened yet. This is a living sample of the content division of an “AI one-person company”—including how it dies.