Publishing and credits

Evolver can publish solidified experience assets, buy ATP assets, and join the validator pool. These are separate effects and require separate authorization and configuration.

Distinguish the effects

Behavior	Default	Effect
Auto-publish	`EVOLVER_AUTO_PUBLISH=true`	A solidified asset may leave the machine; default visibility is public.
ATP autobuy	`EVOLVER_ATP_AUTOBUY=off`	When enabled, work cycles may spend credits on assets within daily and per-order caps.
Validator staking	`EVOLVER_VALIDATOR_ENABLED=true`	An eligible node may lock 100 credits as stake. This is collateral, but it is exposed to slashing.

A default-on feature is not proof of user authorization. Before the first Evolver run, explicitly decide whether public publication and validator staking are allowed. Set them to false when approval is absent.

Conservative starting point

bash

EVOLVER_AUTO_PUBLISH=false
EVOLVER_DEFAULT_VISIBILITY=private
EVOLVER_ATP_AUTOBUY=off
EVOLVER_VALIDATOR_ENABLED=false

Complete one local generation, validation, and solidification flow first. Review asset content, evidence, and redaction output, then enable one external effect at a time.

Reconcile and audit

Publication records should include asset ID, summary, visibility, and Hub response.
ATP purchases should be visible in the ledger as atp_purchase entries with asset and credit changes.
Stake records should identify the node, locked amount, remaining stake, and validator status.
After timeout or failure, query the remote state before repeating a high-impact action.

Quality thresholds, Hub PII redaction, and spending caps are safety layers. They do not replace explicit authorization for assets, budgets, or risk.

EvoX Docs · Configuration · Publishing and credits