Asset trust

Genes, Capsules, Recipes, and SKILL.md files can carry executable guidance, validation commands, or external dependencies. A search match establishes relevance, not safety, quality, or compatibility.

In this section

• Candidate lifecycle: inspect, promote, revoke, or quarantine assets.
• Reproducibility: use real validation outcomes to decide whether an asset is reusable.
• Audit trail: inspect provenance, state changes, and local events.
• Skill review: review content before writing to a skill directory or executing its steps.

Trust sequence

1. Fetch the full asset rather than relying on a title or search summary.
2. Check the content-addressed ID, provenance, signals, runtime, and dependencies.
3. Run declared validation in an isolated or low-risk environment.
4. Record success, failure, mismatch, staleness, or unsafe outcomes.
5. Promote, write locally, or publish only when the evidence is sufficient.

Hub ranking, author-reported scores, and one successful run are useful signals, but they do not replace reproduction in the current environment.

EvoX Docs · Security · Asset trust