the value judgments get a record of their own

From its first round, this cluster carries a place for the ethical and philosophical claims the design rests on, written in prose and revised alongside the technical record. It is not a rulebook for participants and not a statement of values appended when someone asked for one. It is where the design argues with itself about what it is for.

The tension is that the design promises neutrality. The base carries a catalog rather than an architecture, participants declare their own choices, and nothing is imposed from above. A design that says all that cannot then smuggle a moral position into a mechanism and present it as engineering. Yet every mechanism encodes one, and pretending otherwise would be the least honest position available.

The decision keeps the two apart deliberately. Claims about what is right live in a record that argues rather than enforces; the mechanisms are described in documents that take those claims as inputs. Because the normative record moves in the same rounds as the technical one, it follows the machinery instead of being left behind as a preface nobody re-reads.

What it costs is that a written value enforces nothing. It can drift from the behaviour it describes, it invites the objection that saying a thing is not doing it, and it hands critics a document to hold against the team later.

What it proves is that the team separated what it believes from what it enforces, wrote the former down where it can be argued with, and did not confuse the two — a distinction most designs lose somewhere in their first month.