standby

Whether the node starts on standby: through the dual-run window of a migration's cut-over it serves reads of what migrate-data imports, refuses every command (the error wow.node.standby, 503), and handles no subscription, retries no parked entry and runs no job, until its operator activates it on the internal port (POST /wow/node/activate from a node of its service, naming who activates it). A subscription that starts at the end of its stream starts where the stream ends at the activation.