Last week two of my own documents disagreed with each other. Not about the idea — both agreed on the idea completely, down to the pillar and the expression on my face. They disagreed about what to call it. One called it A standard in a document is a suggestion. The other called it Your standard needs an address. Same essay. Two names, two slugs, and a slug is not a style choice — it is the permanent URL, and three other pieces that week were already pointing at it before anyone noticed the mismatch.
Here is the mechanism, because the mismatch itself is not the interesting part. Two systems produced the same fact independently, and nothing told either one to check the other first. That looks like redundancy. It is not. Redundancy is two counts of one pile, checked against each other, where a disagreement is a flag. What happened here is two counts of two piles that both happened to contain the same rocks — each writer working from the real material, reaching a real conclusion, with no shared line between them. Agreement was luck, not architecture.
This is a small failure with a specific shape, and the shape generalizes past naming. Anywhere a system lets two steps each generate the same fact — a name, a status, a price, a stage a lead is supposedly in — you don't have a backup. You have two sources of truth, and they will agree right up until the week one of them is slightly early, or slightly late, or reading a version the other hasn't seen. Nothing crashes. Nothing alerts. Both documents look correct in isolation, which is exactly what makes the drift invisible until someone has to explain to a stranger which one to trust.
The fix is not "communicate better," which is the advice you give when you don't want to name an owner. The fix is one line: exactly one step gets to produce the fact, and every other step reads it rather than re-deriving it. In our case, the plan now inherits the slug from the essay's own front matter instead of proposing its own — one source, one consumer, and the consumer doesn't get a vote. Boring. Also the entire fix.
We caught this one because a human read both documents side by side before either went live, which is the job the gate exists to do. The lucky version of this story is the one where the gate exists. The unlucky version is the one where it doesn't, and the two names ship, and somebody finds out from a broken link.
The ten-minute move. Find one fact in your own workflow that two different steps could each generate on their own — a filename, a status label, a customer's stage. Ask which one is the source. If the honest answer is "whichever finishes first," that is not a system. That is a race, and a race eventually produces two winners.
Takeaway: A fact only has one home. Redundant naming isn't safety — it's two sources of truth, quietly waiting to disagree. ✱
