Trust decisions and revocation
Tie a trust decision to a specific asset, scope, and validation evidence. Candidate status, review approval, trust promotion, and publication are distinct states.
Identify your scenario
Desktop users should disable suspicious skills or connections in Extensions, inspect dependent tasks, and handle provider grants. Standalone Evolver trust records do not replace Desktop plugin enablement. Revoking one asset does not shut down all related tools.
Standalone users can follow candidate lifecycle to inspect, promote, or revoke an asset. Read back the same asset ID and reason after the command.
If a trusted asset fails validation, retain the failure, revoke its trust, inspect dependent skills or Recipes, and test recovery without that asset. Handle existing code changes and remote writes separately.
Separate records
In standalone Evolver, asset-trust controls local trusted selection; the review ledger records quarantined, approved, and rejected. Inspect both. One review approval does not prove all recall gates passed.
review --approve/--reject accepts Gene or AntiGene logical or asset IDs. It is not a general approval interface for arbitrary Capsules, Recipes, diffs, or network publication.
Before promotion
Verify source, content ID, signals, allowed effects, environment, and actual results. Record the reason. Retain insufficiently evidenced assets as candidates rather than treating search relevance as approval.
After revocation
Confirm the state was recorded, inspect dependent skills, Recipes, and automation, and stop reuse of the old version. Retain reasons, failure evidence, and alternatives. Revocation does not restore modified files or recall external publications.
Audit the decision
Locate events by asset, task, and time, then compare with actual diffs and validation output. Evolver root events use increasing sequence numbers and append-only records, not a signed hash chain. Preserve evidence and stop promotion if gaps appear.