Quality signals
Asset quality must come from observable execution and reuse outcomes. Model-reported confidence, download counts, or one success may be useful clues, but none should decide promotion or team adoption alone.
Inspect current signals
bash
evolver asset-health
evolver reuse-report
evolver recall-verify-report
evolver memory-graph status
Evidence hierarchy
| Evidence | Interpretation |
|---|---|
| Validation passes | A specific assertion holds in one environment |
| Cross-environment reproduction | The result is not limited to accidental state on one node |
| Successful real reuse | The asset produced value in a new task |
| Missing, mismatch, and error outcomes | Recall quality, staleness, or scope may be wrong |
| Asset age and dependency changes | Revalidation is due, not automatic invalidation |
| Memory-graph health | Orphans, repetition, or relationship anomalies are diagnostic, not automatic policy |
recall-verify-report provides a GREEN, YELLOW, or RED gate together with success, missing and mismatch rates, errors, latency, and age. The gate is a review entry point, not an auto-publish button.
Administrative action
- GREEN: confirm target environment, impact boundary, and review requirements before promotion.
- YELLOW: collect more reproduction or real reuse outcomes and keep the asset in a pilot scope.
- RED: stop automatic recall or promotion and inspect the asset, index, version, and environment match.
Review cadence
Revalidate high-impact assets after dependency upgrades, platform changes, repeated failures, or long periods without reuse. Reports must retain failures; success-only data produces a misleading quality picture.
Related pages
EvoX Docs · Administration · Asset governance