Candidate lifecycle
Experience fetched from the Hub or created locally should not become trusted merely because it is searchable. Evolver records trust decisions separately from asset content so an asset can be inspected, promoted, or revoked.
Inspect current state
evolver asset-trust list
evolver asset-trust show <asset_id>
Hub assets are marked untrusted when written locally. An unpromoted asset is excluded from trusted Gene selection while remaining available for review and reproduction.
Make a trust decision
evolver asset-trust promote <asset_id> --reason "validated in repository A"
evolver asset-trust revoke <asset_id> --reason "validation no longer passes"
Before promotion, verify provenance, trigger signals, permitted effects, validation commands, and observed results. Revoke an asset that was once trusted when its scope no longer matches, its evidence has expired, or a risk is discovered.
Review decisions
The review ledger uses quarantined, approved, and rejected states. Record a human decision with:
evolver review --approve <asset_id> "evidence reviewed"
evolver review --reject <asset_id> "unsafe command scope"
A human decision takes precedence over later automatic quarantine records. Trust promotion and review approval remain separate records: the first controls trusted local selection, while the second preserves the review outcome.
After revocation
- Inspect the asset again and confirm that the revocation event was recorded.
- Find Skills, Recipes, or automations that depend on it and stop using the old version.
- Preserve the reason and replacement path instead of deleting the original evidence.
Related pages
EvoX Docs · Security · Asset trust