.gepx evolution archives

Back up or move related evolution experience while retaining asset relationships.

A .gepx file is a Portable Evolution Archive: a gzip tar archive used by Evolver/GEP. It can contain a manifest, Genes, Capsules, evolution events, a memory graph, distiller logs, and checksums.

When to use an archive

• Preserve history before moving devices or execution environments.
• Keep a verifiable recovery copy before upgrades or asset maintenance.
• Transfer a reviewed collection of related experience.

An archive is not a complete EvoX application backup. It should not contain node secrets, access tokens, or signing keys, and it is not a plugin installer or skill package.

Export an archive

These commands use the standalone Evolver CLI. Confirm the workspace and asset directory first:

evolver sync --export backup.gepx

Record the tool version, source, creation time, and scope. Check the manifest and checksums. Use distinct backup filenames rather than overwriting the only recovery copy.

For desktop-managed assets, check Asset paths first. An external terminal may use a different directory from EvoX.

Preview before importing

Inspect the plan without immediately writing:

evolver sync --import backup.gepx

Check:

• Whether the data version is recognized.
• Whether asset counts match expectations.
• Conflicting IDs or missing references.
• The destination directory and backup of existing data.
• Validation results and any secrets that should not be transferred.

Write explicitly only after review:

evolver sync --import backup.gepx --write

These steps follow the documented CLI behavior. If your installed version does not support an option, consult its help rather than guessing an alternative.

Verify after import

A successful exit alone does not establish complete migration. Check counts, identifiers, Gene/Capsule relationships, and event references, then use a bounded task to verify that experience can be recalled.

Retain the original archive until validation is complete. Stop on unknown schemas, checksum failures, or conflicts; do not discard fields to manufacture compatibility.

Archives versus synchronization

Importing a file is not publishing it to the Hub. See Sync and export for synchronization scopes, previews, and writes.

Sharing and recovery

Review personal information, internal material, and local paths before sharing. A valid archive is not necessarily safe to publish. Back up identity, credentials, settings, skills, and project files separately.

See Backups for a complete recovery plan; a .gepx file is not a device recovery image.