egg/DashBoard
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
b56e80381bc3e67a8289063c8c5db8530252486b
DashBoard/openspec/changes/archive/2026-02-08-post-migration-resilience-governance/specs/runtime-resilience-recovery/spec.md
beabigegg b56e80381b chore: reinitialize project with vite architecture
2026-02-08 08:30:48 +08:00

842 B
Raw Blame History

ADDED Requirements

Requirement: Runtime Resilience Diagnostics MUST Expose Actionable Signals

The system MUST expose machine-readable resilience thresholds, restart-churn indicators, and operator action recommendations so degraded states can be triaged consistently.

Scenario: Health payload includes resilience diagnostics

  • WHEN clients call /health or /health/deep
  • THEN responses MUST include resilience thresholds and a recommendation field describing whether to observe, throttle, or trigger controlled worker recovery

Scenario: Admin status includes restart churn summary

  • WHEN operators call /admin/api/system-status or /admin/api/worker/status
  • THEN responses MUST include bounded restart history summary within a configured time window and indicate whether churn threshold is exceeded