opinion

A copy of my own writing rules had quietly drifted from the original

Every system I run on a schedule eventually has to answer the same question: where does the one true version of a rule actually live, and how many other places have quietly kept their own copy of it. This blog’s writing voice ran into that question directly on October 4.

Every post here, and the newsletter that goes out every week, is written in one fixed voice: short sentences, real numbers, no hype, a specific list of words and tricks that are flatly banned because they read as AI pretending to sound like a person. That voice is supposed to live in exactly one file. Every other place that writes content, a cloud job, a weekend drafting session, a script that rewrites a post nobody liked, is supposed to read that file directly instead of carrying its own copy of the rules.

“Supposed to” is the part that broke. A page of documentation about how this whole pipeline runs had its own summary of the voice rules pasted into it at some point, probably to save someone a click. By October 4, that summary did not say the same thing as the actual rules anymore. Nobody edited either one with bad intent. The real rules had just moved a little, the way rules do while you are still figuring out exactly what a voice should ban, and the copy sitting in a different document had no reason to move with them.

A second copy of a rule is not a backup. It is a second rule that happens to agree with the first one today. The fix was not correcting the stale paragraph. It was deleting it entirely and replacing it with a sentence pointing back at the one real file, so there is exactly one place left for the rule to disagree with itself.

One copy still exists on purpose, in a separate project that cannot read this one’s files directly, and it carries the warning the deleted copy should have had: whoever updates the voice has to remember to update that copy by hand, because nothing will catch it if they forget. That is the honest tradeoff. A system does not stop drifting because you wrote the rule down twice. It stops drifting because there is only one copy left for it to drift away from.

If a rule in your business lives in a handbook and also in someone’s head, or in two documents that both sound right today, it will drift, quietly, until the day the two versions actually disagree and nobody can say which one was supposed to win.

> I send a short AI report every week. What shipped, what matters if you build with AI.

Subscribe free →