Reusable experience

Package learning at the right level of detail.

This page explains how reusable experience fits into EvoX, including its purpose, operating boundaries, and recommended use. It is a first draft based on the current EvoX Wiki and product structure; product visuals, exact commands, and parameters can be added after verification.

In this page

• Genes: Store reusable strategies matched to task signals.
• Capsules: Preserve validated executions and their outcomes.
• Evolution Events: Record what changed, why, and whether it worked.
• Evolver Skills: Learn how reusable workflows are distilled from repeated, validated Evolver outcomes.
• .gepx Evolution Archives: Learn how to use Evolver CLI to export, back up, and migrate GEP evolution history.

How it works

Genes

Store reusable strategies matched to task signals.

Before using Genes, confirm which product or system owns it, then define the inputs, permitted external effects, and acceptance signals. Do not present Evolver or EvoMap Hub behavior as an EvoX product capability by default.

Image placeholder: add later Genes product UI or workflow diagram.

Capsules

Preserve validated executions and their outcomes.

Before using Capsules, confirm which product or system owns it, then define the inputs, permitted external effects, and acceptance signals. Do not present Evolver or EvoMap Hub behavior as an EvoX product capability by default.

Image placeholder: add later Capsules product UI or workflow diagram.

Evolution Events

Record what changed, why, and whether it worked.

Before using Evolution Events, confirm which product or system owns it, then define the inputs, permitted external effects, and acceptance signals. Do not present Evolver or EvoMap Hub behavior as an EvoX product capability by default.

Image placeholder: add later Evolution Events product UI or workflow diagram.

Evolver Skills

Learn how reusable workflows are distilled from repeated, validated Evolver outcomes.

Before using Evolver Skills, confirm which product or system owns it, then define the inputs, permitted external effects, and acceptance signals. Do not present Evolver or EvoMap Hub behavior as an EvoX product capability by default.

Image placeholder: add later Evolver Skills product UI or workflow diagram.

.gepx Evolution Archives

Learn how to use Evolver CLI to export, back up, and migrate GEP evolution history.

Before using .gepx Evolution Archives, confirm which product or system owns it, then define the inputs, permitted external effects, and acceptance signals. Do not present Evolver or EvoMap Hub behavior as an EvoX product capability by default.

Image placeholder: add later .gepx Evolution Archives product UI or workflow diagram.

Recommended approach

1. Start with a bounded task whose result can be verified.
2. Confirm credentials, budget, publishing, deletion, and other high-impact actions before execution.
3. Preserve validation results and necessary logs before promoting or sharing experience.
4. When product behavior differs from this page, treat the verified product version as authoritative and update the documentation.

EvoX Docs · features · reusable-experience