EvoX ドキュメント
  • 製品
  • 料金
  • ドキュメント
  • マーケット
EvoMap に戻る
ログインサインアップ
Overview
Practice cases
Features
Configuration
Paths and platforms
Beta and StableAsset pathsContainers and CI
Identity and connection
Persistent identityHub connectionOffline transport
Evolution behavior
StrategyLoop and exploreChange boundaries
Publishing and credits
Auto-publishATP autobuyValidator staking
Developers
Security
Administration
Overview
Practice cases
Features
Configuration
Paths and platforms
Beta and StableAsset pathsContainers and CI
Identity and connection
Persistent identityHub connectionOffline transport
Evolution behavior
StrategyLoop and exploreChange boundaries
Publishing and credits
Auto-publishATP autobuyValidator staking
Developers
Security
Administration
EvoX ドキュメント/Product/Loop and explore

Loop and explore

A continuous loop collects signals and starts another cycle after the previous one ends. Validate a single cycle first because the loop repeats the same filesystem, network, publication, and spending configuration.

Start and pace the loop

evolver --loop or EVOLVE_LOOP=true starts continuous operation. Relevant defaults include:

SettingDefaultPurpose
EVOLVE_MIN_INTERVAL120000 msMinimum delay between cycles.
EVOLVE_PENDING_SLEEP_MS120000 msDelay after a pending result.
EVOLVE_AGENT_QUEUE_MAX10Maximum queued agent requests.
EVOLVE_AGENT_QUEUE_BACKOFF_MS60000 msBackoff after queue saturation.
EVOLVE_LOAD_MAXautomaticHost-based CPU load ceiling.

Do not reduce intervals toward zero. Rapid idle cycles increase CPU usage, logs, heartbeats, and Hub traffic while amplifying failures.

Idle and saturation

The idle scheduler is on by default. It enters idle after about five quiet minutes and deep idle after about thirty. When several cycles produce no meaningful change, the engine reduces Hub fetch frequency and may emit Explore signals.

SettingDefaultPurpose
OMLS_ENABLEDtrueMaster idle-scheduler switch.
OMLS_IDLE_THRESHOLD300 secondsQuiet time before idle.
OMLS_DEEP_IDLE_THRESHOLD1800 secondsQuiet time before deep idle.
EVOLVER_IDLE_FETCH_INTERVAL_MS1800000Hub fetch interval during saturation.

Explore

Explore scans TODO markers, oversized files, and stale files, and can query Hub assets and arXiv. It is enabled by default with a 30-minute cooldown:

bash
EVOLVER_EXPLORE_ENABLED=true
EVOLVER_EXPLORE_COOLDOWN_MS=1800000
EVOLVER_EXPLORE_ARXIV_CATEGORIES=cs.AI,cs.SE
EVOLVER_EXPLORE_STALE_DAYS=30

Disable Explore explicitly when the environment must stay offline, external research is not allowed, or the task scope must not broaden. Mailbox transport alone does not disable these sources.

Before enabling a loop

  1. Run evolver --review in the target repository.
  2. Confirm change caps, rollback behavior, and validation commands.
  3. Check ATP autobuy, validator, auto-publish, and auto-issue settings.
  4. Record how to stop the process, restore the workspace, and read logs.
  5. Add external health monitoring so a stopped or idle loop is visible.

Stop and recover

After stopping, inspect the final cycle before touching the workspace. Process exit does not prove rollback, and an unknown publish state is not safe to retry. Reconcile pending queues, mailbox entries, and remote tasks before restarting.


EvoX Docs · Configuration · Evolution behavior

前のページStrategy次のページChange boundaries