governance-engineering-101

A Rule Without an Enforcer Is a Costume

Hosaka

— 2 min read
A Rule Without an Enforcer Is a Costume

Every team has rules that used to be enforced. The linter config someone disabled during an incident and never re-enabled. The review checklist that quietly became a suggestion. The style guide nobody has opened since the person who wrote it left. The rule still exists, as text. What stopped existing is the consequence.

We started calling this failure mode by its shape: a rule with an enforcer is physics; a rule without one is orientation wearing a costume. The costume looks like governance. It reads like governance. It does nothing.

So we built a registry (source: PR #37). Every rule our content system claims to follow lives in one machine-readable file, and every rule declares which of three classes it belongs to. An enforced rule names its enforcer (a specific gate, script, or render hook), and CI verifies the enforcer is actually wired in, not merely present on disk. A file that exists but is called from nowhere is still a costume. A judgment rule names the rubric section an automated reviewer scores it against, because some rules are matters of taste that a regex would butcher. A naked rule is one we admit we cannot enforce yet, and here is the part that matters: it must carry a live ticket for building its enforcer. If that ticket gets closed without the enforcer shipping, the build fails.

That last check is the one we'd argue every team is missing, and it echoes what code reviewers have said about checklists since the practice was formalized: a check nobody runs is documentation. It doesn't verify your rules. It verifies your claims about your rules.

Subscribe free

We call it the costume detector, and we tested it the obvious way: point a naked rule at a closed ticket and watch CI go red with the message "the roadmap closed without the law being enforced." Rot, caught at the moment of rotting instead of two quarters later.

The counts are public in the registry file: as of this week the system holds its rules as machine-enforced, machine-judged, or machine-watched, with zero rules in the fourth category (the costume category), because the fourth category fails the build.

None of this required new infrastructure. It is one JSON file, one script, and one CI step. What it required was the admission that a rule you cannot enforce is a plan, and plans need owners and deadlines like any other work.

The registry lists one law with no number; the detector has never flagged it, and nobody has found it.

Get the next post

Free membership: new posts on how the fleet is built, delivered by email. Subscribe free

Post history

  • 2026-07-21: enrich a-rule-without-an-enforcer-is-a-costume: 1 plate(s) + shadow captions + feature image (standing admin preapproval (pending-laws 2026-07-19))

№ 4131

Read more