FARO Notification Service - Requirements Document

Summary

Created comprehensive requirements document for FARO, a standalone notification service to handle all notification capabilities for Aura (and potentially other RCI applications).

Document Location

/home/rci/.claude/plans/cuddly-wiggling-harp.md

Key Features

Core Capabilities

• Multi-channel delivery (Email via Microsoft Graph API, WhatsApp via Twilio)
• 7 distribution lists to migrate from Aura
• 8 notification types with configurable settings

Safeguards & Controls

• Per-recipient daily limit (default 5/day)
• Fingerprint-based deduplication (15-min window)
• Batch approval queue (5+ recipients)
• Circuit breaker for failures

Advanced Features

• Notification digest mode (aggregate alerts at 8am Argentina time)
• Unsubscribe mechanism with token-based links
• Subscription management per user/notification type

API Surface

• 20+ REST endpoints for notifications, lists, types, subscriptions, batches, history
• Public unsubscribe endpoint (no auth)
• AI-discoverable documentation pattern (following reports.roderickc.com)

Admin UI

• Dashboard with stats
• Distribution list management
• Approval queue
• Subscription viewer
• Digest configuration
• Daily limit monitoring
• Notification history with export

Development Phases

1. MVP: Email + Lists + Logging + Auth
2. Control: Dedup + Limits + Rate limiting + Approvals
3. UX: Types + Subscriptions + Unsubscribe + Admin UI
4. Advanced: Digest + WhatsApp + Webhooks + Multi-tenancy

Migration Strategy

Lists 9 Aura files to update with FARO client after development.

---

Status: Requirements complete, development on hold pending FARO project start.