ReadonlybackendFor: (record: FleetRecord) => ProvisioningBackendReadonlycanaryTenantTags: readonly string[]Optional Readonlyclock?: () => numberOptional ReadonlyfinalizedStateProviderFor?: (record: FleetRecord) => FinalizedOrdinaryStateProvider | undefinedReadonlyrecords: readonly FleetRecord[]Optional ReadonlyrouteAttestation?: AttestConvergedActiveRouteOptionsReadonlysecretsFor: (record: FleetRecord) => DeploymentSecretsOptional ReadonlysettlementFor?: (record: FleetRecord) => FleetSettlementHost | undefinedThe host to hand each settled promotion to, per deployment.
Optional, and its absence changes nothing about correctness: every promote path attests what it published whether or not a host is settling, because checking its own work is the package's obligation rather than a service it performs for a caller.
provisionDeployment deliberately consults nothing like this. A first
deploy returns synchronously to the caller that asked for it, so the host
already knows the moment it went live and can settle after the call using
attestFleetRecordActiveRoute; an in-lease settlement point there would
add a callback into the critical section to tell a caller something it is
about to be told anyway.
ReadonlyspecFor: (record: FleetRecord) => DeploymentSpecReadonlystore: FleetStateStore
Tuning for the convergence wait each post-promote attestation performs. The defaults suit every provider this package targets; a caller overrides them to bound the wait differently or to drive it from an injected clock.