Roadmap
Implementation plan and delivery status.
Work proceeds in numbered steps. Each step must leave main buildable and must not break prior behavior.
Completed
| Step | Scope |
|---|---|
| 01 | Foundation: CLI, config, logging, exit codes |
| 02 | Canonical model, SQLite, fixture import |
| 03 | Rule engine, first findings, suppressions |
| 04 | Reporting slice (HTML/JSON), offline demo |
| 05 | AWS inventory |
| 06 | AWS cost collection and attribution |
| 07 | AWS metrics and utilization signals |
| 08 | Rightsizing rules and savings estimates |
| 09 | GCP inventory |
| 10 | GCP cost, metrics, pricing, optimization |
| 15 | Cross-provider parity and combined reporting |
Planned
| Step | Scope |
|---|---|
| 11 | Azure inventory |
| 12 | Azure cost, metrics, optimization |
| 13 | DigitalOcean inventory |
| 14 | DigitalOcean cost, metrics, optimization |
| 16 | Terraform correlation |
| 17 | AI assistant (interpret-only; no invented data) |
| 18 | Security, reliability, packaging |
Definition of done
- Behavior implemented and documented for the step scope
- Backward compatible, or migration included
- Tests: success, empty input, malformed input, boundaries
go test ./..., linter, build green- No secrets or customer data in the tree
- Next step consumes documented interfaces
Capability manifests
Each adapter ships a capability manifest covering inventory, billing, metrics, pricing, and supported checks. Collection output and reports state gaps explicitly; adapters do not backfill missing signals.