EvoX 文件
  • 產品
  • 價格
  • 文件
  • 能力市集
返回 EvoMap
登入註冊
概览
实践案例
功能
配置
开发者
安全
管理
开始管理
节点清单运行策略上线清单
发布管理
构建与签名验证与晋级平台覆盖
资产治理
生命周期决策技能版本质量信号
蜂群运维
工作节点与任务共享工作拓扑健康
运行与恢复
监控备份事件响应
概览
实践案例
功能
配置
开发者
安全
管理
开始管理
节点清单运行策略上线清单
发布管理
构建与签名验证与晋级平台覆盖
资产治理
生命周期决策技能版本质量信号
蜂群运维
工作节点与任务共享工作拓扑健康
运行与恢复
监控备份事件响应
EvoX 文件/Security & Operations/运行策略

Runtime policy

Runtime policy narrows what the software can do into what this node is allowed to do. The same installation should use different policies for personal development, a pilot, and a long-running service.

Decisions to make

AreaPolicy question
EvolutionWhich repair, optimize, innovate, or explore intents are allowed, and whether loops are continuous
NetworkWhich Hub may be used and whether heartbeats, task claims, and asset fetches are allowed
PublishingWhether auto-publish is allowed and which assets require human review
WorkerWhether local and Hub switches are enabled and what scheduling capacity is advertised
ValidatorWhether the node joins validation, accepts staking, and claims tasks each cycle
BudgetWhether ATP auto-buy, credit spending, or other paid behavior is allowed
ExecutionFile and line caps, forbidden paths, validation commands, and rollback points

Conservative baseline

text
WORKER_ENABLED=0
EVOLVER_VALIDATOR_ENABLED=0
EVOLVER_AUTO_PUBLISH=false
EVOLVER_HARD_CAP_FILES=<task-specific limit>
EVOLVER_HARD_CAP_LINES=<task-specific limit>

This is an administrative baseline, not a requirement that every environment use identical values. Validator participation may be enabled when connected to the Hub; a node that does not accept staking or validation work should opt out before its first run. ATP auto-buy is off by default and needs per-order and daily limits before enablement.

Change policy safely

  1. Record the reason, owner, target nodes, and effective time.
  2. Apply to one pilot and run doctor, status, and the planned validation.
  3. Check task, publishing, spending, and event records against expectations.
  4. Expand only after the pilot is stable; restore the previous configuration and restart affected processes on failure.

Review periodically

Review whenever node purpose, ownership, Hub connection, or cost boundaries change. Do not assume a feature that was disabled in one version keeps the same default after an upgrade.

Related pages

  • Rollout checklist
  • Network authorization

EvoX Docs · Administration · Getting started

上一篇节点清单下一篇上线清单