Asset governance
Asset governance separates “an experience was generated” from “the team or network may depend on it.” Genes, Capsules, Recipes, and Skills should retain distinct provenance, evidence, and version relationships.
In this section
- Lifecycle decisions: operate candidate, promotion, revocation, and publication states.
- Skill versions: manage
SKILL.mdwrites, updates, and rollback. - Quality signals: combine validation, reuse outcomes, and environment fit.
Governed objects
| Object | Primary evidence |
|---|---|
| Gene | Trigger signals, strategy, constraints, validation commands, and reuse outcomes |
| Capsule | Inputs, result, validation, and environment from one complete execution |
| Recipe | Ordered Gene/Capsule steps and expression result |
| Skill | Host-facing instructions, scripts, dependencies, and permissions |
Do not skip local validation because an asset was published, downloaded, or matched in search. Every governance decision should trace back to a specific asset ID, version, and evidence set.
EvoX Docs · Administration · Asset governance