GEP schemas
GEP uses separate objects for how to act, what happened in one execution, and whether the result is trustworthy. Keeping those objects separate preserves provenance, validation, and applicability boundaries.
Core objects
| Object | What it records | What to check before use |
|---|---|---|
| Gene | A reusable strategy, trigger signals, and an execution approach. | Whether it applies to the current environment and whether its steps remain valid. |
| Capsule | A validated execution outcome with the Gene, evidence, and context it used. | Gene references, validation evidence, and environment assumptions. |
| Evolution Event | The process, selection, result, and lifecycle signals for one evolution attempt. | Whether it traces to the corresponding task and artifacts. |
| ValidationReport | A reproduction and verdict for a candidate asset or claimed result. | Environment, commands, exit status, key output, and conclusion. |
| Memory | Relationships, outcomes, and reuse history used for local recall. | Whether it belongs to the current agent or project and whether it is stale. |
Local storage
Evolver normally keeps local GEP data under assets/gep/, using JSON or JSONL stores for Genes, Capsules, Events, and the memory graph. Configuration can relocate these paths.
Do not put the following into assets:
node_secret, access tokens, signing keys, or production credentials.- Unexplained full transcripts or personal information.
- Machine-specific absolute paths without explicit environment assumptions.
Construct and validate
- Decide whether the object represents a strategy, execution outcome, or validation report; do not put every concern into one free-text field.
- Use stable identifiers to relate Genes, Capsules, Events, and reports.
- Run schema and content validation before writing or publishing.
- Preserve source, version, validation result, and current-project evidence for external assets.
When using MCP, evolver_asset_validate can run publication-oriented redaction and quality checks before publishing, but it does not replace tests in the current project.
Version compatibility
Stop promotion or publishing when a schema is unknown or a reference is missing. Migration tooling may transform known versions, but dropping fields is not valid compatibility.
Related pages
EvoX Docs · Developers · Build with GEP