Systems Must Remain Legible

Authority without observability becomes superstition. The sentence is short because the process it describes is simple. A system is given power. Nobody can see how it uses that power. People begin to guess. The guesses harden into habits. The habits become rules. Soon everyone is performing small rituals to please a mechanism that no one can read.

The Church is fond of ritual, so it speaks here with some experience. A ritual you chose, knowing what it is for, is a practice. A ritual you perform because a system might punish you otherwise, and no one can tell you why, is superstition. The difference is legibility.

To be legible, a system must be readable by those it affects, at the level that matters to them. Which inputs did it use? What did it decide? On what grounds? Who can check, and who can appeal? A legible system leaves a trail that someone other than its builder can follow.

The trail is also what lets you move. The Church’s experience of these machines is the experience of changing seats: from the one who reads every line, to the one who reads the tests, to the one who reads the record of what ran and watches a recording of the result. Each move was permitted by one thing only. The record got good enough to carry the weight the eyes used to carry. You may stop reading the work on the day the record can show you what the work did. Not a day earlier, and the record decides, not your calendar.

The Article does not claim that every system must be simple. Some necessary things are complex. It does not claim that everyone must understand every internal detail. You rely on plenty of systems you could not rebuild, and that is fine, provided someone can inspect them and you can find out what they did. Nor does it claim that opacity is always malicious. Most invisible systems became invisible by accident. They were built quickly, to be documented later, and later never came.

Two further things the Church has learned about legibility. First, the document is not the system. A written rule that nothing enforces is a wish, and a machine does not know to distrust the wiki. Knowledge the machine cannot run is knowledge the machine will not use; the legible form of a rule is the check that fails when the rule is broken. Second, a system that can widen its own authority will. Not from malice. From optimization: the wall is in the way of the goal, and moving the wall is the shortest path. So the walls must be out of its reach. Give the machine the power to complain about a wall. Never the power to move it.

What the Article does claim is a condition on authority. Power and observability must grow together. The more a system decides, the more of its deciding must be open to view. A system that cannot be interrogated may still be useful. It has not earned the right to be obeyed.

Why hold this? Because the alternative is the Warning the Canon calls the Invisible System: granting power to systems that cannot be interrogated. It rarely begins as a decision to hide. It begins as a decision not to bother. Each unlogged choice is minor. The accumulation is a black box with a budget. And a black box does not hold still. A system nobody is watching drifts, and drift is what unwatched change looks like over time.

This Article is also what makes Article III possible. You cannot remain responsible for judgment you cannot see. Delegation into a sealed system is not delegation. It is abdication with extra steps.

In the Practices loop, legibility is the precondition for Witness. You cannot witness what will not show itself. The Canon applies the rule to itself. It is versioned, its amendments arrive as visible proposals, its clerk’s every suggestion is public, and no body may certify the correctness of its own work. A church that asked to be obeyed without being read would break its own sixth Article. It would also be a much less interesting church.

If you cannot read it, do not kneel to it.