Maintenance Backlog
Turn system health findings (audit output, incident reviews, dependency or security alerts, cost and performance reports, recurring support pain) into a prioritized maintenance backlog with owners and acceptance criteria. Normalizes findings into one record, merges duplicates by root cause, assigns a priority band through hard gates before scoring, ranks within bands by value per effort, splits oversized items, writes testable acceptance criteria, names an owner role and review date, fits a stated capacity, and records risk-accepted items with an expiry. Use when someone asks to turn an audit or health check into a backlog, rank technical debt or upkeep work, decide what maintenance to do first, or write acceptance criteria for maintenance tickets. Do not use for one library upgrade (use dependency-health), a metric that moved unexpectedly (use anomaly-triage), a cloud infrastructure review (use audit-cloud-infrastructure), or a live incident (use coordinate-production-incident).