Struct NodeInput 

pub struct NodeInput<'a> {
    pub config: &'a ServerConfig,
    pub data_dir: &'a Path,
    pub storage: Arc<dyn Storage>,
    pub kv: Arc<dyn KvStore>,
    pub auth: Auth,
    pub options: ServerOptions,
    pub watch_provider: Option<Arc<dyn WatchProvider>>,
    pub provision_tier: ProvisionTier,
    pub messaging: Option<Arc<dyn Messaging>>,
    pub is_leader: CronLeaderGate,
    pub node_id: u64,
    pub worker_exe: Option<PathBuf>,
}

The built store + resolved config handed to assemble. Owns the blob/KV backends and the auth/options the caller already resolved; borrows the parsed config and data directory.

Fields

config: &'a ServerConfig

The full parsed server config (the handler + compute sections are read here).

data_dir: &'a Path

The node data directory (per-site SQL, handler state).

storage: Arc<dyn Storage>

The object store built by crate::blobs::build_blobs.

kv: Arc<dyn KvStore>

The metadata KV, already cache-fronted, built by crate::backends::build_kv.

auth: Auth

The control-plane auth built by crate::auth::configure_auth.

options: ServerOptions

Server options, already carrying the resolved posture, daemon runtime, and (post-configure_auth/configure_oidc) issuer / OIDC verifier.

watch_provider: Option<Arc<dyn WatchProvider>>

The cloud blob-change watch provider (FA-5b2), if the backend is a cloud one.

provision_tier: ProvisionTier

The provisioning tier for the watch provider.

messaging: Option<Arc<dyn Messaging>>

The wasi:messaging substrate override for the handler runtime. None uses the single-node default (LogMessaging over the same backends); the cluster path passes its Raft-backed coordinator.

is_leader: CronLeaderGate

The single leader gate for cron firing + the compute / domain-verify reconcile loops. Single-node passes an always-true gate (there is one node); the cluster passes its Raft is_leader check so a single node drives each sweep.

node_id: u64

This node’s compute scheduler id (0 single-node; the cluster node id in a fleet, so replicas are tagged to the right node).

worker_exe: Option<PathBuf>

The binary the re-exec’d compute workers run as — the container backend’s __sandbox jailer and the microVM backends’ __vmm-run/__vz-run VM hosts. None uses this process’s own executable (current_exe), which is what boatramp serve wants (the child is boatramp). An embedding harness whose own binary doesn’t implement those subcommands should point this at a built boatramp binary, so it can drive the real container/microVM backends in-process (only the per-workload worker re-execs; the serving plane stays embedded). The docker backend needs neither — it talks to a daemon.