Generated by scripts/playbook-coverage.sh from the playbook frontmatter -
do not edit by hand. CI (--check) fails when this file drifts from the
playbooks, so every coverage change shows up in a PR diff.
A zero cell is a coverage gap, not missing data: either a playbook to write or a gap deferred knowingly. The prioritised backlog lives in docs/ROADMAP.md and is weighted by expected recoverable spend, not by cell count.
| waste_category | aws | azure | gcp | cross-cloud | total |
|---|---|---|---|---|---|
| orphaned | 4 | 1 | 1 | 1 | 7 |
| idle | 4 | 1 | 1 | - | 6 |
| overprovisioned | 7 | 2 | 1 | - | 10 |
| commitment-mismatch | 1 | 1 | 1 | - | 3 |
| schedule-blindness | - | - | - | 1 | 1 |
| modernization | 1 | - | - | - | 1 |
| ai-ml-inefficiency | - | - | - | 2 | 2 |
| egress | 1 | - | - | - | 1 |
| total | 18 | 5 | 4 | 4 | 31 |
| confidence | playbooks |
|---|---|
| obvious | 12 |
| likely | 15 |
| possible | 4 |
- idle x cross-cloud
- overprovisioned x cross-cloud
- commitment-mismatch x cross-cloud
- schedule-blindness x aws
- schedule-blindness x azure
- schedule-blindness x gcp
- modernization x azure
- modernization x gcp
- modernization x cross-cloud
- ai-ml-inefficiency x aws
- ai-ml-inefficiency x azure
- ai-ml-inefficiency x gcp
- egress x azure
- egress x gcp
- egress x cross-cloud