finops-analysislisted

# FinOps Analysis ## Purpose Evaluate cloud spending efficiency and produce actionable recommendations for cost optimization across compute, storage, network, and managed services. Align cloud costs with business value through unit economics and cost attribution. ## Scope Constraints Reads cloud billing data, resource configurations, and usage metrics for cost analysis. Does not modify infrastructure or execute provisioning commands. Does not access financial systems beyond cloud cost APIs. ## Inputs - Cloud provider(s) in scope (AWS, GCP, Azure, multi-cloud) - Current monthly spend breakdown or billing export - Application architecture overview (compute, storage, databases, networking) - Business metrics for unit economics (users, transactions, requests) - Any existing cost optimization efforts or commitments ## Input Sanitization No user-provided values are used in commands or file paths. All inputs are treated as read-only analysis targets. ## Procedure ### Progress Checklist - [ ] Step 1: Map cost allocation and tagging - [ ] Step 2: Analyze compute right-sizing - [ ] Step 3: Evaluate commitment-based discounts - [ ] Step 4: Assess spot/preemptible opportunities - [ ] Step 5: Calculate unit economics - [ ] Step 6: Detect cost anomalies and waste ### Step 1: Map Cost Allocation and Tagging - Inventory all cloud accounts, projects, and resource groups. - Verify tagging strategy covers: team, environment, service, cost center. - Identify untagged or mis-tagged re