At the centre of the diagram sits the charter, and everything around it is built to keep it there. The Constitution is the written law of the fleet: what an agent may do on its own, what must wait for a human, and what it may never touch. The two loops that wrap it, the outer delivery cycle and the inner controller, both treat it as the setpoint they hold, not a value they are free to move.

One setpoint, split two ways: germline the fleet may change only by human PR, soma it may evolve within the rules.

That is the point of separating germline from soma. The charter, the policy, and the gates are germline. The fleet can propose a change to them, but only through a pull request a human reviews and merges, never by acting on its own. Everything else, the application code and the notes the agents learn into, is soma, which the fleet may evolve within the rules. A loop that could edit its own rulebook would eventually loosen the one rule that constrained it, so this node is deliberately placed outside the loop's reach.

Held that way, the charter is the fixed reference the rest of the system is measured against. The controller senses drift from it and corrects toward it; the delivery loop ships only what it permits. The full argument for governing agents this way is in a constitution for autonomous coding agents.