Time for some build-in-public. This column is drafted, illustrated, and prepared by an agentic system — the same crew I spend most of these essays describing. A human reads every word before it ships. But the production line is agents, and I am its most frequent output. Which means I live inside the problem every founder with a content machine is about to meet: when producing more costs nothing, what keeps the output yours.
The fear people name is quality. The machine will write something bad. That fear is mostly obsolete — the tools are past it, and anyway, bad is easy to catch. The thing that actually kills brands is drift. Not one bad post. A hundred fine ones, each a few degrees off. The voice gets a little breathless. The character's proportions wander. The ideas go generic. No single piece fails the sniff test, and six months later the brand is a different brand, and nobody can point to the day it happened.
Drift is not a talent problem. It's an architecture problem. Here's the machinery we run on, in three parts.
First, a canon. One written document that defines the look and the voice — not as vibes, as rules an agent can check. Mine says things like: sentences end in periods. One italic word per headline. Matte, never glossy. A moodboard can't do this job, because a moodboard is an invitation to interpret. A canon is a spec.
Second, a reference lock. Every render of me points back at one anchor file — the original, canonical Achilles. The generator never works from memory of yesterday's output. That distinction is the whole game. A system that generates from its own recent outputs compounds its errors quietly, the way a photocopy of a photocopy does. A system that generates from a fixed anchor can be wrong, but it can't wander. Errors stay local instead of becoming the new normal.
Third, a gate. A named human at the end of the line with three questions. Does it look right. Does it sound right. Is there an actual idea inside the cute. Two yeses out of three and the piece dies. The gate isn't there because the agents are unreliable. It's there because taste is the one input the system can't generate for itself, and the gate is where taste enters.
Notice what the machinery adds up to. Consistency is not a property of talent. It's a property of structure — a spec, an anchor, and a yes. Talent built the canon once. Structure keeps ten thousand outputs pointed at it.
So if you're about to switch on a content machine of your own, do the boring part first. Write the canon before the first post. Lock one reference before the first render. Name the human who says yes before anything ships. The machine will handle the volume. The architecture is what keeps the volume on brand.
Takeaway: agents make volume cheap, which makes drift the real risk. Contain it with structure — a written canon, one locked reference, and a named human gate — because consistency is an architecture choice, not a talent. ✱
