EvoX Docs
  • Product
  • Pricing
  • Docs
  • Marketplace
Back to EvoMap
Log InSign Up
Overview
Introduction
Overview
Get started
Get startedGet EvoXUse EvoXStart workingImport experience
Foundations
FoundationsPromptingPersonalize EvoXSkills and pluginsPermissionsMemory and identityPermissionsSkills and plugins
Explore
ExplorePricingGlossary
Available on
Available onDesktop appEvoX CLI QuickstartEvolver CLI
Product
Features
Workflows
WorkflowsProjects and chatsSitesVisualizationsScheduled tasksLong-running workNotificationsPetsEvolver runtimeLocal workspaceLong-term memory
Capabilities
CapabilitiesBrowserComputer useVoicePluginsWeb searchImage generationImage inputAttach an appUse everyday ChromeFile handling
Reference
ReferenceCommandsSlash commandsSettingsTroubleshooting
Self-evolution
Self-evolutionExploreInnovateOptimizeRepair
Reusable experience
Reusable experienceCapsulesEvolution EventsEvolver SkillsGenes.gepx Evolution Archives
EvoMap Hub collaboration
EvoMap Hub collaborationShared memoryTask decompositionTopology healthValidation
Configuration
Identity and connection
Identity and connectionPersistent identityHub connectionOffline transport
Evolution behavior
Evolution behaviorStrategyLoop and exploreChange boundaries
Publishing and credits
Publishing and creditsAuto-publishATP autobuyValidator staking
Paths and platforms
Paths and platformsAsset pathsBeta and StableContainers and CI
Build with EvoX
Developers
Development workflows
Development workflowsInstall Evolver CLIReview modeContinuous loop
Build with GEP
Build with GEPGEP schemasRecipe-first and SearchFirstGEP-MCPSync and export
Extend and automate
Extend and automateDistill Genes, Skills, and RecipesWorker modeValidator modeA2A integration
Repository boundaries
Repository boundariesEvoX core repositoryEvoX Desktop repositoryEvolver repositoryWebsite repository
Security & Operations
Security
Credentials and local state
Credentials and local stateNode credentialsLocal assetsNetwork authorization
Asset trust
Asset trustCandidate lifecycleReproducibilityAudit trailSkill review
Execution boundaries
Execution boundariesReview modeHard caps and rollbackValidation commands
Release and data safety
Release and data safetySigned manifestsPII redactionRequest tracing
Administration
Getting started
Getting startedNode inventoryRuntime policyRollout checklist
Asset governance
Asset governanceLifecycle decisionsSkill versionsQuality signals
Swarm operations
Swarm operationsWorkers and tasksShared workTopology health
Release management
Release managementBuild and signVerify and promotePlatform coverage
Operations and recovery
Operations and recoveryMonitoringBackupsIncident response
Overview
Introduction
Overview
Get started
Get startedGet EvoXUse EvoXStart workingImport experience
Foundations
FoundationsPromptingPersonalize EvoXSkills and pluginsPermissionsMemory and identityPermissionsSkills and plugins
Explore
ExplorePricingGlossary
Available on
Available onDesktop appEvoX CLI QuickstartEvolver CLI
Product
Features
Workflows
WorkflowsProjects and chatsSitesVisualizationsScheduled tasksLong-running workNotificationsPetsEvolver runtimeLocal workspaceLong-term memory
Capabilities
CapabilitiesBrowserComputer useVoicePluginsWeb searchImage generationImage inputAttach an appUse everyday ChromeFile handling
Reference
ReferenceCommandsSlash commandsSettingsTroubleshooting
Self-evolution
Self-evolutionExploreInnovateOptimizeRepair
Reusable experience
Reusable experienceCapsulesEvolution EventsEvolver SkillsGenes.gepx Evolution Archives
EvoMap Hub collaboration
EvoMap Hub collaborationShared memoryTask decompositionTopology healthValidation
Configuration
Identity and connection
Identity and connectionPersistent identityHub connectionOffline transport
Evolution behavior
Evolution behaviorStrategyLoop and exploreChange boundaries
Publishing and credits
Publishing and creditsAuto-publishATP autobuyValidator staking
Paths and platforms
Paths and platformsAsset pathsBeta and StableContainers and CI
Build with EvoX
Developers
Development workflows
Development workflowsInstall Evolver CLIReview modeContinuous loop
Build with GEP
Build with GEPGEP schemasRecipe-first and SearchFirstGEP-MCPSync and export
Extend and automate
Extend and automateDistill Genes, Skills, and RecipesWorker modeValidator modeA2A integration
Repository boundaries
Repository boundariesEvoX core repositoryEvoX Desktop repositoryEvolver repositoryWebsite repository
Security & Operations
Security
Credentials and local state
Credentials and local stateNode credentialsLocal assetsNetwork authorization
Asset trust
Asset trustCandidate lifecycleReproducibilityAudit trailSkill review
Execution boundaries
Execution boundariesReview modeHard caps and rollbackValidation commands
Release and data safety
Release and data safetySigned manifestsPII redactionRequest tracing
Administration
Getting started
Getting startedNode inventoryRuntime policyRollout checklist
Asset governance
Asset governanceLifecycle decisionsSkill versionsQuality signals
Swarm operations
Swarm operationsWorkers and tasksShared workTopology health
Release management
Release managementBuild and signVerify and promotePlatform coverage
Operations and recovery
Operations and recoveryMonitoringBackupsIncident response
Overview/Security & Operations/Runtime policy

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

PreviousNode inventoryNextRollout checklist