{"spec_id":"provider-health-alerting","title":"Spec: Provider Health Alerting from Last-5 Success Rate","summary":"Provider reliability can degrade quickly while still appearing \"configured\" and partially functional. This spec adds a deterministic health alerting contract so when a provider's last-5 execution success rate drops below 50%, the system automatically records a friction event and can optionally push a notification through existing channels, reducing silent failure loops and response latency.","potential_value":0.0,"actual_value":1.0,"estimated_cost":0.0,"actual_cost":1.0,"value_gap":0.0,"cost_gap":1.0,"estimated_roi":0.0,"actual_roi":1.0,"idea_id":"pipeline-optimization","process_summary":"Compute provider health from execution outcomes using a fixed `last_5` window and trigger only when `last_5_success_rate; Automatically write a friction event when the threshold is breached, with provider identity and evidence in event notes.; De-duplicate repeated friction writes while the provider remains degraded; create a new event only on a fresh degradatio; Support optional outbound notification through existing channels (Telegram adapter) behind configuration flags, with no ; Keep usage/readiness alert payloads aligned with the health state so API consumers can observe degraded providers withou","pseudocode_summary":null,"implementation_summary":"api/app/services/automation_usage_service.py (provider health evaluation); api/app/services/collective_health_service.py (health aggregation); api/app/routers/agent_status_routes.py (health endpoints)","created_by_contributor_id":null,"updated_by_contributor_id":null,"created_at":"2026-04-09T03:10:09.005287Z","updated_at":"2026-04-09T03:10:09.005287Z","content_path":"specs/provider-health-alerting.md","content_hash":"e85388dc86aa5b2a","workspace_id":"coherence-network"}