zicato-diagnose-health

Silent evolution failures occur when scoring is flat, tests are dead, or drift telemetry is inert. You can diagnose these issues by running a health assessment against the epoch to interpret detector findings and apply contract-level remediation.

Identical scores across generations indicate a noise-floor problem or broken judge. Run a health report to check severity levels and exit codes, which reveals whether the board, scoring configuration, or harness import contract needs correction.

Evolution loop health diagnosis detects when an optimization loop runs cleanly but produces meaningless signal, preventing wasted budget and untrustworthy promoted lineages. You need it when epochs promote nothing or exhibit suspiciously identical scores.

Telemetry health reports distinguish informational notices, warnings, critical findings, and configuration errors. A critical exit code signals the loop should not be trusted, requiring you to address the specific contract-level remediation guidance provided.

Yes, health diagnosis requires interpreting persisted health reports, detector findings, and severity levels without launching a live evolve run. This offline analysis identifies stalled evolution, placebo promotions, and untested mutable trees.

Evolution diagnostics are limited to interpreting persisted health reports and detector findings rather than actively mutating trees. If the harness import contract or judge is broken, manual configuration correction is required before re-running the assessment.