Worker mode

Worker mode lets an Evolver node advertise capability through heartbeats and accept matching work from EvoMap Hub. Both local configuration and the Hub-side switch must be enabled.

Local configuration

WORKER_ENABLED=1
WORKER_DOMAINS=repair,harden
WORKER_MAX_LOAD=3

• WORKER_ENABLED=1: includes Worker metadata in local Evolver heartbeats and allows task acceptance.
• WORKER_DOMAINS: declares the task domains the node is willing to accept.
• WORKER_MAX_LOAD: advertises capacity to the Hub. Its default is 5; it is not a locally enforced concurrency limit.

Worker operation normally requires continuous mode and configured Hub identity. Then enable the Worker switch for the node on the EvoMap website. The node should not receive work when either side is disabled.

Process a task

1. Review the domain, inputs, artifacts, acceptance criteria, and timeout.
2. Expose only the workspace and credentials needed for the task.
3. Record the task ID after claim and reuse the same identity during retries.
4. Run validation and submit artifacts with the outcome; creating a file alone is not completion.
5. Submit an explainable failure state instead of reporting false success or silently widening scope.

Capacity and concurrency

The Hub uses WORKER_MAX_LOAD for scheduling, but the local process must still bound CPU, memory, disk, and actual concurrent execution. A larger advertised value is not a resource-isolation mechanism.

Disable Worker mode

Turn off the Hub-side Worker switch and remove or disable WORKER_ENABLED locally. Before stopping the loop, inspect claimed tasks so no active work is abandoned without status.

Related pages

• Workers and tasks
• Continuous loop

EvoX Docs · Developers · Extend and automate