Asset publishing and credits

Publication turns local experience into a network asset. Evolver uses an explicit Gene + Capsule bundle flow. The old description of EVOLVER_AUTO_PUBLISH=true publishing after solidify does not enable automatic asset publishing.

Prepare publishable content

A Gene describes the reusable method; its Capsule provides the outcome and verification evidence. They need valid relationships, recognizable schemas, and stable IDs. Review:

• The original issue, environment, strategy, and outcome agree.
• Success evidence comes from execution, not model self-assessment or file creation.
• No credentials, customer material, private conversations, or unrelated code are included.
• Validation commands have acceptable filesystem, network, and resource effects.
• External submission of this specific bundle is authorized.

Check the bundle first

Replace placeholders with actual Gene and Capsule IDs or file paths:

evolver publish --gene <gene-id-or-path> --capsule <capsule-id-or-path> --json --dry-run

Dry-run checks the bundle and gates and enters the applicable Hub validation flow. It is not offline and does not publish the final assets. Inspect gates, blocking reasons, and credit information, not just the exit code.

Blockers include invalid schemas, missing bundles, unproven Genes, failed quality gates, unsafe validation commands, detected leaks, authentication, and insufficient credits. Fix the corresponding problem without dropping evidence or weakening gates.

Publish explicitly and inspect the receipt

After reviewing content and authorization, remove --dry-run:

evolver publish --gene <gene-id-or-path> --capsule <capsule-id-or-path> --json

Keep asset IDs, final status, receipt, Hub reasons, and actual credit information. queued is not approval or public availability. After a timeout, lost response, or partial success, reconcile remote state before retrying.

Local verification bindings and revalidation

Assets claiming successful execution require verification binding from the current local host. Client hashes, external receipts, and historical success claims do not replace authorization from the local ledger. For verification_required, inspect the local verifier and binding, then explicitly run:

evolver publish --gene <gene-id-or-path> --capsule <capsule-id-or-path> --reverify --json

--reverify invokes the local isolated verifier, stores new assets, and continues publication. Original assets remain unchanged. It cannot be combined with --dry-run, --repair, or HUB_DRY_RUN. Without a supported native verifier on the current platform, keep assets as drafts rather than bypassing verification.

After an interruption or recovery response, reconcile source_asset_ids, new asset_ids, and the local ledger before retrying. Do not blindly re-run verification, roll back stored assets, or revoke valid receipts. Redaction that changes bound content requires verification of the new content; the original verification cannot authorize modified assets.

Reference assets versus execution evidence

reference_only is the public Hub path for reference integrity: an immutable Gene + Capsule pair without a local execution-success claim. It supports neither revalidation, repair, nor private Hub, and does not automatically compose a Recipe. stored_reference confirms storage of a reference record, not successful execution. This path awards 0 credits.

Separate local storage from external submission

Local creation, review, reuse, and network publication have separate entry points. Disabling an old auto-publish variable does not prove all external submission has stopped. Inspect active hosts, hooks, Proxy, background tasks, and upload settings.

Server-side detection does not replace pre-publication review. After a leak, stop further sending and revoke or rotate affected credentials. Deleting a local file cannot retract content already sent.

Spending consent and validator eligibility

Track publishing, purchasing, and staking separately. Inspect ATP authorization sources with evolver atp status, persist disabling with evolver atp disable, and check environment overrides. See ATP autobuy for limits and order handling.

Validator staking management owns eligibility, locked funds, returns, and penalties. Accepted publication grants neither validator eligibility nor staking consent; purchasing consent is separate.