OptionalassertOptionalassertOptionaldeleteOptionaldeleteOptionaldeleteOptionalapplication: ApplicationBindingTopologyOptionaldescribeOptionalensureOptionalensureOptionalfindOptionalforceOptionalinspectOptionalreleaseOptionalrevokeStamp the database's ownership sentinel and seed its initial execution fence row.
initialExecutionFenceState is a REQUIRED option rather than backend
configuration because it is a per-provisioning decision: the same control
plane brings ordinary deployments up open and migration targets up locked.
It carries no default anywhere on this path — a migration target that came
up open would be executing exactly when it must not.
It rides an OPTIONS object rather than a fourth positional because this method is implemented by every backend and faked by every test that builds one: the next piece of provisioning context to reach the seeding protocol would otherwise mean a fifth positional and the same fan-out again, and positional four and five of a five-argument call are exactly where a transposed argument compiles and provisions the wrong thing.
Provider truth about what is ROUTED, never desired state.
inspect()answers a different question — "does the deployment the control plane WANTS exist and match?" — and deliberately pins a staged candidate that is receiving none of the traffic, so a converge can compare against it before promoting it. That makes it the wrong instrument for asking what is serving requests: a candidate uploaded and never promoted answers as though it were live. This method answers only the second question and never pins a candidate; the two views stay separate on purpose.Read-only and lease-free. Provider GET/HEAD requests bypass the external mutation fence, so a caller holding no deployment lease may attest, and a caller already inside one does not nest a second.
Refuses rather than guessing: a Worker splitting traffic across versions, a hostname routed nowhere, or a routed artifact carrying no fleet specification digest all throw
ActiveRouteAttestationErrorcarrying what the provider did report. There is no highest-percentage fallback — an attestation is either unambiguous or it is a refusal.