the founder, filed as a participant

There is a dedicated artifact in this cluster for the founding identity, built with the same participant model as anyone else: a self-describing manifest, owned artifacts, and agreements that express what it may do.

The tension is that a point of origin cannot be derived from anything, which is why designs tend to write it into the protocol as a constant. A constant is simple, permanent, and invisible. The alternative is describing the founding position in the same vocabulary as every other position, which is more work and makes it visible.

The decision is the alternative. The founding identity exists in the record as a participant — not a special case in the machinery, but a case the machinery describes. Its authority is expressed the way authority is expressed everywhere here: as an agreement someone can read, in the same format, at the same level.

What it costs is that the founding position's powers become inspectable, and therefore arguable, and anything the design might have preferred to leave implicit now has a document attached to it. It also means the founding identity must be maintained like any other artifact, by people who will not always be its founders.

What it proves is that the team applied its own model to the position with the strongest reason to be exempt. A model of authority that carves out its author is a description of who is in charge; a model that includes its author is a description of how authority works. This record chose the second and paid the visibility for it.