Import experience

Use a .gepx Portable Evolution Archive to back up or migrate Genes, Capsules, Evolution Events, and memory data between supported Evolver/GEP environments.

.gepx belongs to Evolver/GEP. Current material does not confirm an EvoX Desktop import UI; the workflow below uses Evolver CLI.

Prepare the import

• Keep an untouched copy of the source archive.
• Record source, creation time, tool version, and destination environment.
• Inspect the manifest, schema versions, asset counts, and checksum information.
• Perform the first import in an isolated, low-risk environment rather than a production asset store.

Preview and import

Preview the import plan first:

evolver sync --import backup.gepx

Review schemas, destination paths, asset counts, and conflicts. Then write explicitly:

evolver sync --import backup.gepx --write

Preview and explicit --write are separate steps. A command that exits without error does not prove assets were written.

Verify the result

1. Compare manifest counts with imported counts.
2. Check relationships among Genes, Capsules, and Events.
3. Review skipped, conflicting, failed, and unsupported entries.
4. Use a low-risk task to confirm expected experience can be recalled.
5. With MCP, evolver_recall can support the recall check, but it does not replace count, reference, and checksum validation.

Export a backup

evolver sync --export backup.gepx

Record archive path, creation time, tool version, and checksum information. Do not include node_secret, access tokens, or signing keys, and do not overwrite the only backup.

Difference from Hub synchronization

Hub synchronization uses an explicit scope and previews the plan by default:

evolver sync --scope purchased
evolver sync --scope published
evolver sync --scope all
evolver sync --scope all --write

Recipe-first search and lower-level SearchFirst are read-only retrieval paths. They do not silently persist third-party assets. Only explicit sync, import, or publishing operations create the corresponding persistence or external effect.

Failure and recovery

Stop on unknown schemas, checksum failure, or ID conflicts. Preserve the source archive and original environment, then identify what was already written before retrying or recovering.

EvoX Docs · overview · Get started