| Service | Tooling & Access | Observability | Deployment Safety | Paging Health | Total |
|---|
Each service is scored 1–5 on four criteria. The total score is the sum (max 20).
How complete is the service's tooling coverage and operator access in NCL?
| 5 | All tools available and accessible in NCL; no gaps identified |
| 4 | Minor gaps (e.g. one tool missing access for a single operator) |
| 3 | Moderate gaps (e.g. Mechanic namespace missing or multiple access requests pending) |
| 2 | Significant gaps blocking routine operations |
| 1 | Critical tooling unavailable; operators cannot perform basic tasks |
Source: Task 2.3 Tooling Audit
Are dashboards and metrics in place for the service in NCL?
| 5 | All dashboards verified working in NCL; no broken links or missing metrics |
| 4 | Minor gaps (e.g. one sub-dashboard 404 or cosmetic metric missing) |
| 3 | Moderate gaps (e.g. key operational dashboard missing or multiple broken links) |
| 2 | Significant gaps; operators lack visibility into service health |
| 1 | No NCL dashboards or metrics available |
Source: Task 2.4 Dashboard Audit. Scored on dashboard inventory completeness and link liveness only (67 dashboards catalogued; InternalDNS has 2 broken links; Lookout has a single dashboard). Black-mirror metric render-verification from an iso-e host is still outstanding, so a full score of 5 is not yet attainable for any service. DaaS rows share one combined dashboard inventory pending per-plane split.
Are pipelines healthy with functioning rollback alarms?
| 5 | All NCL stages have verified rollback alarms with live metrics |
| 4 | Minor gaps (e.g. one stage with placeholder alarm) |
| 3 | Moderate gaps (e.g. multiple placeholder alarms or missing gamma stage) |
| 2 | Significant gaps; most NCL stages lack functioning rollback |
| 1 | No rollback alarms or pipeline not deploying to NCL |
Source: Task 2.5 Pipeline Audit
Is the service's paging behaviour healthy — appropriate severity, low noise, timely resolution?
| 5 | Consistent appropriate severity; low noise ratio; timely ADC-led resolution |
| 4 | Minor issues (e.g. occasional over-paging or single slow resolution) |
| 3 | Moderate issues (e.g. frequent severity mismatches or recurring noise) |
| 2 | Significant issues; high noise ratio or repeated escalation failures |
| 1 | Paging fundamentally unhealthy; majority of pages mis-severed or unresolved |
Source: Task 2.1 Sev2 Tracking Solution. Scored from engagement-verified out-of-hours Sev2 event counts Jan-Jul 2026 (noise proxy: 0 events=5, 1-2=4, 3-5=3, 6+=2). Per-service resolution-time and severity-mismatch detail not separately available.