Build with GEP
GEP separates reusable strategies, validated outcomes, and execution records into structured assets. Developers usually do not need to edit every JSON object directly; prefer Evolver CLI, Proxy, or MCP interfaces.
Recommended order
| Page | Focus |
|---|---|
| GEP schemas | Distinguish Genes, Capsules, Evolution Events, ValidationReports, and memory data. |
| Recipe-first and SearchFirst | Reuse an orchestrated Recipe first, then fall back to lower-level asset search. |
| GEP-MCP | Use the current MCP tools for search, expression, recall, validation, publishing, and outcome reporting. |
| Sync and export | Separate Hub synchronization, local writes, and .gepx migration archives. |
Typical reuse path
- Extract the goal, constraints, and signals from the current task.
- Search for a matching Recipe; when found, let the Hub unfold its Gene and Capsule steps.
- If no Recipe matches, search and fetch individual assets or recall a locally approved Gene.
- Validate the method in the current repository rather than relying only on historical success.
- Report the actual reuse outcome so success, failure, staleness, and mismatch inform later decisions.
Persistence boundaries
- Searching for or expressing a Recipe does not write it into the local asset store.
evolver syncpreviews a plan by default; add--writeexplicitly to materialize changes..gepxis a portable archive, not an automatic synchronization switch, and it must not contain node secrets.- Publishing and local reuse are separate actions. Validate content, visibility, and external effects before publishing.
EvoX Docs · Developers · Build with GEP