Candor about enforcement

Every constraint a system names carries a second fact that matters at least as much as the constraint. A rule enforced by a gate that runs on every path is one kind of object. A rule enforced by a checklist step nothing blocks is another. A rule with a name, a rationale, and no mechanism whatsoever is a third, and in almost every document ever written all three appear in the same confident present tense.

The mechanism is that a stated constraint is read downstream as an enforced one unless the statement says otherwise, which means the enforcement tier is not metadata about the claim but part of the claim, and leaving it out is not neutrality but a quiet upgrade of a request into a promise.

The web has run this experiment twice with almost identical architectures and opposite results. The Robots Exclusion Protocol has organized crawler behavior since 1994 and was finally standardized as RFC 9309 in 2022, and it is advisory by construction, stating rules a crawler is asked to follow rather than any the protocol enforces. Everyone in the field knows this. The ecosystem works anyway, and it works because the request has always been honest about being a request; nobody who relies on it believes it stops a determined crawler, so nobody’s plan depends on it doing so. Do Not Track ran the other way. A browser header announced a preference, nothing checked it, and to a person toggling the setting it looked exactly like a control. The gap between the look and the fact stayed open until the W3C closed its Tracking Protection Working Group in 2019 without the Do Not Track header ever becoming an enforced standard, and browsers quietly removed the switch. Same enforcement in both cases, which is to say none. Opposite reputations, because one of them said so.

There is a version of this discipline you can practice on your own documents, and it is uncomfortable in a specific and useful way. In our database governance canon every stated principle carries a label for the enforcement it actually has: a guard runnable locally on every commit, a guard that needs a live database, a procedural step nothing blocks, and a fourth label meaning the principle is stated and no mechanism exists at all. The file ends with a register of the gaps, ranked by priority, with a proposed mechanism for each. Read cold, the document looks like a confession. Read carefully, it is the only version of that document anyone can act on, because a reader can now tell which rules protect them and which rules merely describe the intentions of the people who wrote them.

The instinct that resists this is the belief that silence is the safe middle. It is not. A disclosure that names a constraint and says nothing about how it is enforced does not leave the reader neutral; it leaves them assuming, and the assumption always runs in the flattering direction. When the truth surfaces later, and it surfaces at the worst possible moment because that is when anyone checks, what they learn is not that you had a gap. Every system has gaps. What they learn is that you knew and let them believe otherwise, and that lesson attaches to every other sentence you have ever published.

So say requested where requested is the truth. Say procedural where a runbook is all that stands between the rule and its violation. Keep the list of things you have declared and do not yet enforce, and put it where the declarations are rather than in a private tracker. The honest inventory reads worse and travels further, because a reader who can see exactly which of your promises are load-bearing has been handed something rare enough to be worth trusting: a document that gets more credible the harder it is checked.