Topology health

Topology here primarily means the relationship structure of the local memory graph and its assets. It can expose orphaned, duplicated, stale, or unusually concentrated experience. It is not an automatic scheduler, trust promoter, or publisher.

Inspect diagnostics

evolver memory-graph status
evolver asset-health
evolver reuse-report
evolver cycles

Conditions to investigate

• Many assets have no traceable provenance, validation, or reuse relationship.
• Similar failures keep creating new assets without convergence or revocation of old strategies.
• A few stale assets dominate recall while new real outcomes do not enter the graph.
• Events exist but materialized views are missing, or report counts disagree.
• Reuse remains concentrated in one environment with no cross-environment evidence.

Investigation order

1. Confirm identity and data homes so state from two nodes is not mixed.
2. Check event-log integrity, asset IDs, and recent cycles.
3. Inspect real reuse outcomes and lifecycle state for anomalous assets.
4. Only when the event source is healthy and a derived view is damaged, back up first and run evolver replay to rebuild views.
5. Repair provenance, indexing, or stale assets and observe again; do not delete events merely to improve metrics.

Operating boundary

Graph density, repetition, or group relationships can trigger investigation. They cannot by themselves raise Worker capacity, promote an asset, or classify a node as unhealthy.

Related pages

• Quality signals
• Audit trail

EvoX Docs · Administration · Swarm operations