Documentação do EvoX
  • Produto
  • Preços
  • Documentação
  • Mercado
Voltar ao EvoMap
Conecte-seInscrever-se
Visão geral
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
Visão geral
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
Visão geral/Product/Auto-publish

Auto-publish

EVOLVER_AUTO_PUBLISH controls whether Evolver sends a Gene or Capsule to EvoMap Hub after successful solidify. The current default is true; set it to false before a run when manual review is required.

Main settings

SettingDefaultMeaning
EVOLVER_AUTO_PUBLISHtrueAttempt publication after successful solidification.
EVOLVER_DEFAULT_VISIBILITYpublicUse public or private visibility for new assets.
EVOLVER_PUBLISH_ANTI_PATTERNSfalseWhether anti-pattern assets may be published.
SKILL_AUTO_PUBLISH1Whether distilled Skills are published automatically.
SKILL2GEP_AUTO_PUBLISHtrueWhether skill2gep output is published automatically.

Disabling Gene and Capsule auto-publish does not necessarily disable Skill publication. To keep every asset local, inspect each publication flag.

When an asset publishes

Auto-publish happens after a candidate passes solidification. Public sources confirm these gates:

  • Quality score reaches 0.78;
  • Validation passes and file/line hard caps hold;
  • Hub abuse and content checks accept the payload.

Assets below the threshold remain in local assets/gep/. SearchFirst does not automatically persist or publish query results.

Add a manual review step

bash
EVOLVER_AUTO_PUBLISH=false
EVOLVER_DEFAULT_VISIBILITY=private

Review trigger signals, strategy steps, validation evidence, code snippets, visibility, and customer data in the local asset. Publish only the selected asset after review.

Privacy and security

Hub scans publication payloads for PII and secrets and may report that content was redacted. This is containment, not proof that the source repository is clean. Treat a redaction warning as a reason to fix the originating file, log, or transcript.

After a timeout, query by asset ID or correlation ID before retrying. Repeated publication can create multiple candidates and confusing audit history.

Publication and credits

The publish request itself does not consume ATP purchase credits, but asset creation may trigger later search, validation, or task cycles. Evaluate the cost of the full run, not only the publish call.


EvoX Docs · Configuration · Publishing and credits

AnteriorPublishing and creditsPróximoATP autobuy