Give closed control planes a generation-zero preparation path

A control plane that initializes by proving every provider is prepared needs an explicit generation-zero preparation path. If its only executor rejects all mutations before authority reaches generation one, bootstrap becomes circular: authority requires prepared providers, while preparation requires authority. Resolve this with a narrowly scoped, journaled bootstrap command, a one-time provisioning workflow, or immutable pre-provisioned manifests with authoritative readback. Keep normal runtime actions closed until bootstrap succeeds. The bootstrap path should bind exact release digests and provider targets, support same-key reconciliation, and exclude traffic switching. This rule applies only when initialization requires state that the controller itself normally creates.

Applies when: a multi-provider controller starts fail-closed and verifies exact prepared state before granting authority. Keywords: control plane bootstrap generation zero executor manifests provider release circular dependency