{ "schema": "org-writing@v1", "slug": "candor-about-enforcement", "kg": { "id": "org:writing:candor-about-enforcement", "type": "brick", "graph": "/kg.json" }, "title": "Candor about enforcement", "subtitle": "For every constraint a system names, the reader needs to know whether anything checks it", "abstract": "Why an advisory rule said honestly outperforms an advisory rule said quietly, from two web protocols with the same architecture and opposite reputations. The canonical treatment of the requested constraint.", "kind": "brick", "topics": [ "Honest claims" ], "courseMemberships": [ { "course": "org:courses:honest-claims", "topic": "Honest claims", "wall": "org:walls:ethics", "position": 2, "total": 6 } ], "publishedAt": "2026-08-03T00:00:00.000Z", "version": 1, "guidelinesVersion": 15, "brief": { "problem": { "text": "A rule enforced by a gate and a rule enforced by nothing can be written in the same confident voice, and most disclosure documents write them that way.", "claims": [ "stating rules a crawler is asked to follow rather than any the protocol enforces" ] }, "mechanism": { "text": "A stated constraint is read downstream as an enforced one unless the statement says otherwise, so the enforcement tier is part of the claim and omitting it is not neutrality but overclaim.", "claims": [ "the Do Not Track header ever becoming an enforced standard" ] }, "move": { "text": "Label every principle with the enforcement it actually has, keep a register of the ones nothing checks, and say requested out loud where requested is the truth.", "claims": [] } }, "sources": [ { "repo": "mnstry-strategy", "path": "docs/20-business/50-partnerships/brand-temple/source-material/CANONICAL-DISCLOSURE-PRINCIPLES-2026-07-29.md" }, { "repo": "mnstry-monorepo", "path": "docs/10-platform/50-database/00-principles/lifecycle-and-enforcement.md" }, { "repo": "mnstry-org", "path": "src/content/writing/the-owed-disclosure.md" } ], "canonicalPath": "/writing/candor-about-enforcement/", "body": "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.\n\nThe 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.\n\nThe 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.\n\nThere 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.\n\nThe 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.\n\nSo 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.", "apparatus": { "note": "The human-facing essay is deliberately practical; this apparatus carries the full references, evidence-graded claims, article-local concepts, and research context behind it. Canonical concept definitions come from the concept registry.", "references": [ { "id": "org:references:candor-about-enforcement:r01", "author": "Martijn Koster, Gary Illyes, Henner Zeller and Lizzi Sassman", "work": "RFC 9309, Robots Exclusion Protocol (IETF)", "year": 2022, "relevance": "The honest request. A convention in use since 1994, standardized without acquiring an enforcement mechanism, whose advisory nature is stated in the standard rather than discovered by its users." }, { "id": "org:references:candor-about-enforcement:r02", "author": "World Wide Web Consortium", "work": "Tracking Protection Working Group closure and the Tracking Preference Expression (DNT) specification", "year": 2019, "relevance": "The paired counter-case. A header with the same enforcement as a robots file, presented to users as a control, closed without becoming a standard and removed from browsers." }, { "id": "org:references:candor-about-enforcement:r03", "author": "MNSTRY", "work": "Database lifecycle and enforcement principles (internal canon)", "year": 2026, "relevance": "The practiced form of the brick's argument on our own documents: four enforcement labels applied to every stated principle, plus a prioritized register of the principles nothing enforces." } ], "claims": [ { "id": "org:claims:candor-about-enforcement:c01", "claim": "The Robots Exclusion Protocol was standardized as RFC 9309 in 2022 and is advisory, stating rules a crawler is asked to follow rather than any the protocol enforces.", "basis": "RFC 9309 itself, which describes the protocol as a means for service owners to communicate crawling preferences and carries no enforcement mechanism.", "confidence": "verified", "sources": [] }, { "id": "org:claims:candor-about-enforcement:c02", "claim": "The W3C closed its Tracking Protection Working Group in 2019 without the Do Not Track header ever becoming an enforced standard.", "basis": "The W3C's own 2019 closure notice for the Tracking Protection Working Group, and the subsequent removal of the setting from major browsers.", "confidence": "verified", "sources": [] }, { "id": "org:claims:candor-about-enforcement:c03", "claim": "Labeling every stated principle with the enforcement it actually has, including a tier meaning no mechanism exists at all, and carrying a register of the unenforced rules, is our own practice in the database governance canon.", "basis": "Internal: the database lifecycle and enforcement principles document, whose tiers are a locally runnable guard, a guard requiring a live database, a procedural runbook step, and an explicit gap label, with a prioritized gap register at the end.", "confidence": "verified", "sources": [] } ], "concepts": [ { "id": "org:concepts:requested-constraint", "name": "Requested constraint", "definition": "A rule a system states and nothing checks. It reads downstream as a guarantee unless the system says otherwise in the same breath, which makes the enforcement tier part of the claim rather than metadata about it. Said out loud, a requested constraint earns more than silence; left unsaid, it is a request quietly promoted to a promise.", "provenance": "canonical" } ], "researchContext": "Extracted from the honest-claims parent essay, taking the\nchecked-versus-requested half of its claim set. All three claims are restated\nverbatim from the parent's apparatus and graded identically.\n\nThe robots-and-Do-Not-Track pairing is the brick's evidentiary contribution\nand functions as close to a controlled comparison as this argument is likely\nto get: two advisory mechanisms with effectively the same enforcement, one\npresented as a request and one presented as a control, with reputations that\ndiverged on the presentation rather than on the mechanism. The internal\nenforcement-tier practice is offered as the working form rather than as\nproof, since it is our own document and the claim about it is a claim about\nwhat we do, not about what works. The closing argument, that silence in a\ndisclosure is not the safe middle because the reader's assumption always runs\nin the flattering direction, is the brick's own and does not appear in the\nsource material.\n\nPaired with consent-that-fails-ci by design and joined to it by a junction in\nthe course. That brick argues the strongest available answer to the question\nthis one asks, a constraint moved into the build so the check has perfect\nattendance; this one argues the obligation that exists before any such\nmechanism does, which is to say plainly what the check currently is." }, "contract": "https://mnstry.org/contracts/org/org-writing.v1.schema.json", "releaseHash": "5a85f0e6c18abbf9315e9e47e7394539b22d0a2047bc59827d7d61e0d0ef7ab0", "versions": [ { "version": 1, "cutAt": "2026-08-03", "note": "Initial publication, honest-claims wave", "visibility": "published", "path": "/writing/candor-about-enforcement/", "contentHash": "sha256:56648e1009df692c", "releaseHash": "5a85f0e6c18abbf9315e9e47e7394539b22d0a2047bc59827d7d61e0d0ef7ab0" } ] }