The ratchet

Every standard worth having arrives after the work it governs. Somebody decides that type below a certain size is unreadable, or that credentials never enter a source repository, and by then a hundred files already disagree. The two ordinary responses are both losses. Turn the check on and the build goes red on other people’s half-finished work, which means the check is disabled by Thursday and the standard is dead with its reputation attached. Write the standard down as an aspiration instead and it binds nothing, which is the same death with better manners.

There is a third arrangement, and it is one sentence long. List the known breaches, give each one a reason, and rule that the list may only ever get shorter.

Our own type floor works this way. The site’s foundation configuration carries an exceptions entry naming one file and four specific font sizes that fall below the minimum, and the entry’s reason field is not a shrug. It records that these are pre-existing breaches from earlier illustration work, listed so the floor is enforced from here rather than cleaned up inside a design somebody else still has in flight, and it closes with the sentence that does the real work. This list may only shrink. The validator says the same thing in its own comment, treating the enumerated set as a ratchet, passing exactly those sizes and failing the build on any new one.

The mechanism is that the exception is enumerated rather than general, so the check stays green on the precise breaches a person has already examined and red on every new one, which makes the standard binding from today forward without requiring the past to be paid off first.

Written that way, an exception stops being a hole and becomes an inventory. Each entry names a file, a value, and a reason a reviewer can act on, which means the debt is visible, countable, and attached to somebody’s reasoning rather than to a general permission. And the list has a direction. Adding to it is a change a reviewer sees and has to defend; removing from it is free. Nothing about that arrangement is clever. It simply arranges the friction so the easy path points at the standard.

Which is why the failure mode is the blanket. Our boundary rule engine handles this at the other end of the workspace, where a project may exempt certain paths from a content rule, and it rejects the wildcard patterns by name. An exception has to carry a rule, a repository, real paths, and a reason of more than a few characters, or it is refused. The comment above that code says why in a sentence we have not improved on. A blanket exception is not an exception, it is switching the rule off. The distinction is not pedantry, because the two look identical in a configuration file and only one of them can be audited.

The pattern has a name outside software, and the people who named it were solving a harder version of the same problem. Article 4.3 of the Paris Agreement, adopted in 2015, requires that each country’s successive climate commitment represent a progression beyond its current one, which is precisely a list that may only shrink, negotiated among parties with every incentive to loosen it later. Practitioners call it the ratchet mechanism. Its designers understood that the binding force of a commitment made by people who will not be in the room in twenty years comes from the shape of the instrument, not the sincerity of the signatories, and that a floor which can be lowered was never a floor.

That is the part worth carrying into a codebase meant to outlast the people writing it now. A backlog is a statement about intentions, and intentions leave when their owners do. A ratchet is a statement about what the build will accept tomorrow, made in a file the build actually reads, and it keeps its promise long after everyone who made it has moved on to something else.