What happens when an idea meets a system

A rule you have to remember is not a system.

I didn't arrive at that sentence through thinking. I arrived at it through a failure. This site had a written rule: database migrations are applied by hand. The rule was clear, it sat in the documentation, everyone knew it. One migration got forgotten.

Here's what happened. Every query reading that column failed, the read layer fell back to seed data, and for 24 hours the site served the sample data instead of the 23 real records in the database. The build passed. The type check passed. Four separate browser audits passed. None of them lied — an empty list renders as "no results," not as an error.

That was the day it became obvious that writing the rule down one more time would not fix it.

Three levels

Since then I place every rule at one of three levels, and knowing which level it sits at matters more than the rule itself.

Level one: prose. The rule lives in a document. Following it depends on a person remembering in the moment. The failure above happened here. Prose only works when the person reading it was going to do the thing anyway, which is the case where it adds nothing.

Level two: a signal. The rule becomes a command and violations become visible. That was the answer to the migration failure: one command compares the migration files against the live schema and names what's missing. The legal layer has four audit scripts, and all four are deliberately signals, not gates — none of them stops a build.

That's a deliberate choice. A gate that blocks legitimate work either blocks the work or gets bypassed, and both kill the signal. Warn, don't block.

Level three: structural impossibility. The rule disappears, because violating it can no longer be written.

The legal links in this site's footer aren't typed by hand; they're derived from the document index. Writing a link to a page that doesn't exist is structurally impossible. There is no rule saying "remember to check the links," because there can't be.

The same pattern shows up elsewhere: three separate surfaces ask whether an article's body is long enough to be indexed — the detail page, the sitemap, and the language layer. All three call the same function. They cannot drift, because they don't have separate answers to drift between.

Level three isn't free either

On the day I wrote this I found a bug that lands exactly here.

The article list page filtered the articles it displayed by language. It derived the filter chips from the unfiltered raw list. The result: the English page rendered a filter chip taken from the tag of a Turkish-only record. The chip appeared, it was clickable, and it found nothing.

The structure existed, but two branches were fed from two different sources. Structural impossibility only works if you genuinely share the source. Looking like you share it isn't enough.

One more detail: the flaw was invisible while there was no data. With all nine articles empty the list was empty and no chip appeared at all. It surfaced the day the first article was published. An audit run against empty data doesn't count as an audit.

The rule that enforces itself

My favourite example is in the legal imprint. An unknown field is never guessed; it's left null — and a null field renders on the site as a visible "missing" badge.

Seven fields are missing today, and visitors see that as plainly as I do. The rule isn't "remember to fill in the imprint." The rule is that what you leave blank cannot be hidden. Compliance doesn't depend on memory, because the violation is visible.

That's exactly where an idea differs from a system. An idea is a true sentence. A system is the machinery that makes violating that sentence expensive or impossible.

What I don't know

I don't think every rule can be moved to level three, and I don't know whether every rule should be. "Comments carry measurement, not intent" is a written rule in this repo and it sits at the prose level. Could a script check it? Partly, probably. It hasn't been tried.

Something else is open too: I haven't measured what building structure costs. Deriving the filter chip from a single source took five minutes. The legal link index took a day. Right now I decide which rule deserves which level by instinct, and that is precisely the thing I'm trying to avoid.