| Phase | Duration | Milestones | Owner | |-------|----------|------------|-------| | | 4 weeks | • Policy Store schema & CI pipeline. • Draft DSL parser & validation tests. | Architecture / Backend | | B – Tier‑Management Service | 6 weeks | • Event‑driven policy evaluator. • Kafka topics & schema registry. | Core Services | | C – Object‑Mover Workers | 5 weeks | • Multi‑cloud copy adapters (S3, Glacier, Azure Blob, Tape). • Integrity verification suite. | Platform Engineering | | D – Integration | 3 weeks | • Hook TMS into SDMS Core metadata updates. • End‑to‑end test harness (simulated 10 M objects). | QA | | E – Observability | 2 weeks | • Prometheus exporters, Grafana dashboards. • Alert rules for migration failures > 0.1 %. | DevOps | | F – Security Review | 1 week | • Pen‑test of TMS APIs. • KMS key rotation policy. | Security | | G – Release & Roll‑out | 2 weeks | • Canary deployment to 5 % of customers. • Post‑deployment validation. | Release Engineering | | H – Post‑Release | Ongoing | • Policy updates (as legal changes arise). • Cost‑optimization monitoring. | Product Ops |