Planned Features
The documents in this directory are design specifications for features that are not yet implemented. They define the target behaviour, table schemas, API endpoints, and UI components for each feature. They serve as the blueprints for future implementation work.
Implementation Priority
| Priority | Feature | Document | Key Dependencies |
|---|---|---|---|
| High | Delta decomposition | ../architecture/delta-decomposition.md | Core tables exist, needs API endpoints + UI |
| High | Actions & remediation | actions.md | Needs action_types/suggestions/log tables, suggestion_engine, action_executor |
| High | Multi-account | multi-account.md | Needs aws_accounts table, account_discovery, cross-account wrapper |
| High | Budget rules | budget-rules.md | Needs budget_rules/rule_violations tables, rule_evaluator |
| High | Anomaly detection | anomalies.md | Needs anomalies/notifications tables, anomaly_detector, Slack integration |
| Medium | Multi-platform | multi-platform.md | Needs GitHub/CF/DD collectors |
| Medium | Forecasting & changelog | forecasting.md | Needs daily_snapshot, forecaster, cost_forecasts table |
| Medium | Shared cost allocation | shared-costs.md | Needs allocation_rules/allocated_costs tables, cost_allocator |
How to Implement a Feature
- Read the design doc for the feature
- Create the database migrations (see planned migrations 011-024 in schema.md)
- Implement the collector(s) in
components/collectors/ - Add API endpoints in
components/api/src/ - Build UI components in
components/ui/src/ - Add tests following the phase checkpoint approach in testing.md