Note future integration goal for live cloud provider data

Capture that Infrastructure (and likely Glance) KPI data should eventually
come from real provider APIs (AWS, Linode, etc.) via user-supplied API
keys, for pricing/budget/utilization/region data instead of static mocks.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BbJV5nm8KPVH1oNJYKpnoF

design-decisions.md

@@ -80,3 +80,20 @@
 - Bottom row: 2 columns (65/35)
 - Network Traffic card has its own background image at low opacity
 - User avatar dropdown has: Profile, Appearance, Security, Help & Support, Sign Out
+
+---
+
+## Future Integration Notes
+
+### Live Provider Data (AWS, Linode, etc.)
+- All KPI/status card data (resource counts, health, pricing, budgets, cost breakdowns,
+  utilization, regions/map data) is currently mocked/static.
+- The Infrastructure page (and likely Glance) should eventually integrate with real
+  cloud provider APIs — AWS, Linode, or any other VPC/cloud provider — via user-supplied
+  API keys, to pull live data such as:
+  - Resource inventory/counts and health status
+  - Pricing and budget/cost data (replacing the static Cost Breakdown numbers)
+  - Resource utilization metrics
+  - Region/datacenter info for the Infrastructure Map
+- Design the data layer so it's provider-agnostic (a common interface/adapter per
+  provider) since users may connect more than one provider's API key.