Local experience asset management
This page covers viewing and deleting local Genes and Capsules in Desktop. Skill-file updates, standalone Evolver trust promotion, and Hub publication use their own workflows.
Locate an experience
Find the entry in EvoMap's local assets list or open a Gene or Capsule detail from the self-evolution page. Check its type, identifier, content, and origin before keeping or deleting it. Events record what happened and are not deletable Gene or Capsule assets.
Identify the object that needs to change
A local asset entry, task history, installed skill file, and Hub publication are different managed objects. Match type and ID when names appear in several places. Local deletion removes the specified stored experience; it does not clean up every related object.
| Intended result | Does this page complete it? | Follow-up |
|---|---|---|
| Remove a local Gene or Capsule | Yes, through the detail deletion action | Refresh the local list and match the ID |
| Stop using untrusted experience | Deletion alone is insufficient | Check task dependencies and applicable review/trust decisions |
| Roll back an installed skill | No | Restore a validated skill-file version |
| Withdraw a Hub publication | No | Use the owning Hub's publication procedure |
| Undo files changed by a task | No | Recover or compensate from that task's change record |
Scenario: a failed task left an experience entry
Locate the failed stage before judging the experience. A model connection interruption, external-service failure, and inapplicable experience require different responses. Deleting every related asset because a task failed removes objects needed for investigation.
If review establishes that an entry should be removed, record its ID, provenance, and failure evidence, inspect consuming tasks, and back up content needed for recovery. After deletion, verify local removal and task disposition separately. A historical task reference to the asset ID records past use; it does not establish that deletion failed.
Before deleting
- Confirm the target is a local Gene or Capsule, not a similarly named skill, project file, or remote publication.
- Preserve the asset identifier and validation evidence. Complete a backup first if a recovery copy is needed.
- Select Delete in the detail view and confirm the target in the dialog.
- Wait for the result and refresh the list to confirm removal. Service unavailability or a failed operation is not completed deletion.
Deletion has no recycle-bin restore and does not undo file changes, external actions, or Hub publications. Removing a local entry does not withdraw a network asset. See asset state and adoption decisions for standalone Evolver trust handling.
If deletion fails or the object remains visible
Reopen details for the same asset ID and refresh the list, confirming the application and local asset source. If the service is unavailable, follow Desktop service maintenance, then check the actual result. Do not bypass an error by manually deleting storage files.
Local and Hub publication lists have different scopes. A remaining remote entry does not establish that local deletion failed. Handle remote withdrawal separately through the owning Hub's publication process.
Completion criteria
The target type and identifier are confirmed, the operation result agrees with the refreshed list, and dependent tasks have been checked. Retain source and validation evidence for investigation rather than hiding history by deleting events.