10c3c43a75
Ship the full Communication portal (real SMS API, feature-locked future channels), BFF proxy, docs, snapshot, and phase handover. Co-authored-by: Cursor <cursoragent@cursor.com>
3.0 KiB
3.0 KiB
Communication Platform Roadmap
Torbat Communication — Production Ready for SMS MVP (Phase 8 complete).
Completed work → progress.md. Phase doc → communication-phase-8.md.
Handover → phase-handover/phase-8.md. Snapshot → service-snapshots/communication.yaml.
The Communication service is feature-complete for the current MVP scope. Items below are future roadmap only — not registered phases and not in scope until explicitly product-scoped.
Current Production Scope (Complete)
| Capability | Status |
|---|---|
| SMS (mock + Payamak) | Production Ready |
| Provider registry + failover + circuit breaker | Production Ready |
| Template engine | Production Ready |
| Dynamic contact sources | Production Ready |
| Queue + DLQ + delivery tracking | Production Ready |
| Business OTP (non-auth) | Production Ready |
| Incoming webhooks | Production Ready |
| Health / capabilities / monitoring | Production Ready |
Future Channels (Not Implemented)
Architecture-ready stubs exist; real adapters are deferred:
| Channel | Provider kind (stub) | Notes |
|---|---|---|
smtp |
SMTP adapter + sender identities | |
| Push | fcm |
FCM + device token registration |
whatsapp_cloud |
Cloud API + template approval alignment | |
| Telegram | telegram_bot |
Bot API adapter |
| Rubika | rubika_bot |
Region-specific social messaging |
| Voice | voice_gateway |
Call status webhooks; OTP voice path |
Optional Operations Enhancements (Not MVP)
| Item | Notes |
|---|---|
| Dedicated Celery worker | Reuse QueueEngine.process_due; optional ops |
| Redis-backed rate limiter | Replace in-process limiter at scale |
| Prometheus metrics exposition | Platform ops standard TBD |
| Outbox dual-write / bus consumers | Platform message bus maturity |
| Core OTP handoff | Requires explicit ADR; auth OTP stays on Core today |
Cross-Service Integration (Consumer-Owned)
Other services integrate via Communication APIs/events only — connector phases belong to those services:
| Consumer | Phase | Responsibility |
|---|---|---|
| Delivery | 10.9 | Notification client + app API contracts |
| Experience | 11.9 | Widget + notify client contracts |
| Sports Center | 9.8 | CRM/Loyalty/Communication/Accounting adapters |
| Hospitality | 12.7 | Multi-platform connector bundle |
Longer Term (Platform)
- Notification service as thin consumer of Communication (roadmap.md item 26)
- Smart Messenger + legacy SMS panel alignment (prefer Communication per ADR-012)