Execution Nodes
Enroll and operate Execution Nodes, including panel-neutral automatic execution, runtime readiness and remote Silo capability.
Bridge → Host Fabric → Execution Nodes enrolls and operates additional execution locations for managed Silos.
Add a Node
Create the Node from Bridge and follow the enrollment details shown there. Install the current Core on the Node and complete the Node setup using that enrollment. Bridge finishes Node setup automatically.
Availability
A Node can remain ready while idle. If its last status is old, refresh or wake it before treating stale information as an outage.
Worker controls
Use Start, Stop or Restart only when those controls are available for the Node's configured runtime. If the Node uses a hosting scheduler or another supported background path, Bridge reports that mode instead of exposing controls that cannot work.
Silo placement
Bridge shows the Silos currently assigned to the Node and its available capacity. A Silo keeps the same public and Admin URL when placed remotely.
Diagnostics
Node Diagnostics reports placement, local Site/storage inventory, current Host contact, routing state, runtime/worker status, software version and per-Silo availability without exposing private Site content.
Update a Node
Node + Core updates are Host-managed. Refresh an idle Node before applying an update so Bridge works from current state.
Remove a Node
Move or delete its Silo placements first. Remove the Node only when Bridge reports that it is safe to remove.
Emergency isolation
Use the supported Node override or quarantine flow when an unhealthy Node must stop serving before normal recovery can complete. Recovery, retirement and destructive cleanup remain separate operator decisions.
