one vocabulary, one pattern, every level

A stack this tall invites a bespoke mechanism at each level. The record refuses that too, and the refusal is visible in the words: one vocabulary is applied across the whole cluster in a single round, and one pattern repeats at every level — a level is a catalog for the level below it, its entries are agreements, entries are retained because someone carries their cost, and the topmost level is itself a set of agreements rather than an authority sitting above them.

The tension is that recursion is elegant and can be vacuous. Turtles all the way down is a joke about a design with no ground. The counter-argument in the record is a claim about what is finite: the rails are finite, the agreements are not. Whatever the design can do, it can do because some agreement says so, and agreements can be added without adding machinery.

Naming was part of the decision, not decoration. The levels were given fixed names and those names were pushed through every component in the same pass, so that a world, a universe, and the things above them mean the same thing in every description. A vocabulary applied unevenly is how a system acquires two incompatible models of itself.

The cost is that no level is privileged: there is no vantage point from which the rest can be debugged, and fixing the top lets you assume nothing about what sits beneath it. What it proves is that the team chose one pattern and reproduced it deliberately, instead of accumulating a different mechanism per layer and calling the accumulation a design.