reflex-audit

Auditing reflex chains involves scoring trigger usage, failure recovery, and consistency from trigger-stats.json and historical workflow runs. It computes weighted dimension scores and produces a prioritized report for scheduled system reviews and post-incident diagnosis.

Fixing an imbalanced reflex-chain workflow requires applying targeted repairs to the relevant workflow documents and circuit breaker state. The process preserves historical counters while addressing the underlying failure mode identified during the audit.

Performing a quick repair involves interpreting the reported issue, pinpointing the relevant reflection, applying a repair plan, and validating via targeted end-to-end tests. It uses trigger-map definitions and trigger-stats.json to ground changes in observed behavior.

Yes, reflex audits apply to scheduled system reviews by evaluating trigger coverage, efficiency, and definition consistency. It reads SSOT trigger-map definitions and historical workflow runs to generate a structured health report.

Assessing circuit breaker health requires trigger-stats.json, SSOT trigger-map definitions, and historical workflow runs. These inputs allow the audit to score CB health alongside failure recovery and workflow balance dimensions.

Imbalanced trigger usage after an incident indicates failing or imbalanced reflection behavior. An audit computes weighted dimension scores from trigger-stats.json and historical runs to pinpoint weaknesses and recommend targeted improvements.