.gepx evolution archives

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

A .gepx file transfers evolution assets. These commands target Evolver: sync --export writes a JSON package with type, version, export time, Gene or Capsule assets, provenance, and sync records. The JSON package does not include the complete event stream, memory graph, or distiller logs. Verify other export entry points separately.

When to use an archive

• Preserve Gene and Capsule assets 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 asset counts and provenance, and compute a file digest for verification after transfer. Use distinct backup filenames rather than overwriting the only recovery copy. Packages have a 64 MiB limit; split export scope when needed.

For desktop-managed assets, check Asset paths first. Check the external terminal and EvoX asset directories separately.

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

Inspect command arguments in help before execution. Stop when an option is unsupported rather than guessing an alternative.

Verify after import

A successful exit alone does not establish complete migration. Check counts, identifiers, Gene/Capsule relationships, provenance, and sync records, then use a bounded task to verify recall. Restore and validate root events and memory state separately.

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 Back up and move devices for a complete recovery plan; a .gepx file is not a device recovery image.