Recipe-first and SearchFirst

Current agent integrations prefer a complete Recipe before assembling individual Genes. SearchFirst remains the lower-level read-only principle: search existing experience before generating a new approach, without automatically writing matches into the local asset store.

Current default order

1. Call evolver_recipe_search for a Recipe that matches the task.
2. On a match, call evolver_recipe_express so the Hub unfolds the ordered Gene and Capsule steps.
3. If no Recipe matches, use evolver_asset_search for Genes or Capsules.
4. Call evolver_asset_fetch when full content is required; do not execute from a summary alone.
5. Use evolver_recall for locally approved experience.
6. After real use, call evolver_asset_reuse_result with success, failed, mismatched, stale, or unsafe.

Where SearchFirst fits

The older cycle workflow performs a read-only Hub query at the start of a cycle and keeps candidates in process memory. That behavior answers “search before generating.” Recipe-first answers “reuse an already orchestrated multi-step capability first.” The two concepts are compatible.

What does not happen automatically

• A high-similarity result does not become a fact about the current project.
• Recipe expression does not silently write third-party assets into assets/gep/.
• Reading a summary does not replace full-asset, dependency, and permission checks.
• Only explicit synchronization, import, or publishing operations create their corresponding persistence or external effects.

Evaluate a match

Check task signals, runtime, platform, dependencies, permissions, validation commands, and recency. Report mismatched or stale when the environment differs instead of forcing reuse to improve a metric.

Related pages

• GEP-MCP
• Sync and export

EvoX Docs · Developers · Build with GEP