Sone-071 Upd Instant

| FR # | Description | |------|-------------| | | Notification Scheduler Service – a new micro‑service ( notification-scheduler ) that stores schedule definitions and triggers delivery jobs. | | FR‑02 | CRUD API – POST /schedules , GET /schedules/:id , PUT /schedules/:id , DELETE /schedules/:id . All endpoints secured via OAuth2 scopes notification:write/read . | | FR‑03 | Schedule Model (MongoDB / PostgreSQL) – fields: id , name , channel (email/push/in‑app), audienceQuery (JSON), templateId , scheduleType (once/cron), runAt (UTC), timeZoneMode (user‑local / fixed), maxPerUserPerDay , maxPerUserPerWeek , createdBy , createdAt , updatedAt , version . | | FR‑04 | Template Service Integration – reuse existing template-service for rendering tokens. | | FR‑05 | Delivery Worker – background worker (Node/Go) that reads ready schedules, resolves audience, expands tokens, respects throttling, and calls the appropriate channel provider (SES, Firebase, internal in‑app). | | FR‑06 | Throttling Store – per‑user counter with TTL (Redis). Increment on each successful send; reset after 24 h or 7 d as per schedule config. | | FR‑07 | Audit Log – write to an append‑only notification_audit table (or event‑store). Include action , actorId , scheduleId , payloadDiff . | | FR‑08 | Metrics Exporter – Prometheus‑compatible metrics ( notifications_sent_total , notifications_failed_total , notifications_rate_limited_total ). | | FR‑09 | UI Components – React (or Angular) pages: Schedule List , Schedule Detail/Edit , Wizard Modal , Audit Timeline , Metrics Dashboard . | | FR‑10 | Access Control – Only users with role MARKETER or ADMIN can create/edit schedules. Read‑only for ANALYST . | | FR‑11 | Error Handling & Retries – exponential back‑off for transient provider errors (max 3 retries). Persist failures with reason. | | FR‑12 | Internationalization – templates may include i18n keys; scheduler must pass locale from user profile to template renderer. |

In SONE-071, her acting chops are on full display. Rather than simply going through the motions, Ogura excels at conveying emotional shifts—from playful and coy to overwhelmingly vulnerable and immersed in the moment. For fans of her work, this title serves as a prime example of her evolution from a standard idol into a highly skilled performer. SONE-071

| NFR # | Requirement | |-------|-------------| | | Scalability – Scheduler must support up to 500k active schedules and 10 M deliveries per day . Use partitioned tables + sharded Redis for throttling counters. | | NFR‑02 | Availability – 99.9 % SLA for the Scheduler API (5 xx errors < 0.1 %). Deploy across two AZs. | | NFR‑03 | Latency – API response < 200 ms for CRUD ops; delivery worker latency < 5 s from scheduled time to provider call. | | NFR‑04 | Security – Data at rest encrypted (AES‑256); transport TLS 1.2+. Auditable actions stored immutably (WORM). | | NFR‑05 | Compliance – Support GDPR “right to be forgotten”: deleting a user must also purge any pending scheduled notifications for that user. | | NFR‑06 | Observability – Structured logs (JSON) with correlation IDs; tracing via OpenTelemetry. | | NFR‑07 | Testing – 80 % unit coverage, 70 % integration coverage, end‑to‑end UI tests with Cypress. | | NFR‑08 | Performance – Bulk audience resolution (≤ 10 k users per batch) must complete in < 2 s. | | FR # | Description | |------|-------------| |