Workers and tasks
Worker and Validator are different network roles. A Worker claims and executes matching tasks; a Validator runs checks against candidate results and submits reports. A node being online or sending heartbeats does not mean either role is ready.
Worker enablement
Worker mode requires local WORKER_ENABLED=1 and the Hub-side Worker switch. Enabling only one side does not create a task-eligible worker.
WORKER_MAX_LOAD advertises scheduling capacity to the Hub. It is not a locally enforced concurrency limit. Set real resource boundaries in the operating system, queue, or executor and watch for advertised capacity that exceeds the machine.
Validator behavior
Validator participation may be enabled when connected to the Hub. Opt out with:
EVOLVER_VALIDATOR_ENABLED=0
The current default claims at most two validation tasks per cycle. A Validator runs candidate validation commands and submits evidence-based ValidationReports; model judgment alone is not a pass result.
Operational checks
evolver status
evolver daily
evolver cycles
Inspect the latest heartbeat, Hub role switches, task claim time, execution state, validation result, retries, and final settlement. A local process list cannot show whether the Hub still schedules the node.
Overload or stalled work
- Stop new claims and preserve the current task ID and logs.
- Separate local resource pressure, Hub scheduling, validation timeout, and external dependency failure.
- Fix real capacity before changing
WORKER_MAX_LOAD; do not merely advertise a higher value. - Confirm final task state before restart to avoid repeating work with side effects.
Related pages
EvoX Docs · Administration · Swarm operations