Sone-071 Info
| FR # | Description |
|------|-------------|
| FR‑01 | 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. |
| Feature | Details | |-------------|-------------| | Crystal purity | Grown via floating‑zone laser melting, yielding < 10 ppm impurity levels. | | Ionic conductivity | 5 mS cm⁻¹ at 25 °C; activation energy 0.18 eV (vs. 0.3–0.4 eV for earlier Na‑NASICON). | | Electrochemical stability window | 2.8 V vs. Na/Na⁺ (stable up to 4.5 V vs. Na metal). | | Mechanical robustness | Young’s modulus ≈ 85 GPa; can withstand > 1 % strain without fracture. | | Processability | Can be thin‑slab‑pressed to 20 µm thickness, enabling high‑energy‑density cell designs. | | Compatibility | Works with Na‑metal anodes, Na₃V₂(PO₄)₂F₃ cathodes, and emerging prussian‑blue‑derived cathodes. | SONE-071
| Q | A | |------|------| | Is SONE‑071 safe to handle? | Yes. It is a ceramic material; no flammable solvents. Standard PPE (gloves, goggles) is sufficient. | | Can it be retro‑fitted into existing Li‑ion factories? | Partially. The pressing and sintering steps are compatible with current solid‑state pilot lines; electrode coating equipment needs minor adjustments. | | Will it work with sodium‑ion liquid electrolytes? | Technically possible as a dual‑ion system, but the performance advantage is realized only in all‑solid‑state configurations. | | Is there any risk of sodium metal reacting with moisture? | As with any Na‑metal cell, strict dry‑room or glove‑box handling is required for the anode side. The electrolyte itself is moisture‑stable up to ~ 1 % RH. | | FR # | Description | |------|-------------| |
| # | As a … | I want … | So that … |
|---|--------|----------|-----------|
| US‑01 | Product marketer | A “New Notification” wizard that asks for channel, audience filter, schedule (date‑time or recurring), and message template | I can launch a campaign without developer help |
| US‑02 | Product marketer | Time‑zone aware scheduling (auto‑detect from user profile) | Recipients receive the message at a sensible local hour |
| US‑03 | Product marketer | Dynamic token insertion (first_name, plan_type, last_login) | Messages feel personal, driving higher CTR |
| US‑04 | Product marketer | Delivery throttling (max 3 per user per 24 h, 10 per week) | We avoid spamming and stay under compliance limits |
| US‑05 | Customer Success | Audit log showing who created/modified a schedule, timestamps, and version diff | We can investigate any delivery issues or compliance queries |
| US‑06 | Data Engineer | Metrics endpoint (/notifications/metrics) exposing sent, delivered, opened, click‑through counts per schedule | We can monitor campaign health in our dashboard |
| US‑07 | QA Engineer | Test harness to simulate time‑zone based deliveries & throttling | Automated regression coverage | | Q | A | |------|------| | Is
Title: Advanced Smart‑Search with Contextual Filters
Ticket: SONE‑071
Product Area: Search (frontend + backend)
Target Release: v3.4.0 (Q3‑2026)
Stakeholders:
Problem Statement
Users currently can only type a free‑text query and optionally select a static list of filters (date range, status, tag). They must manually combine multiple filters and often get irrelevant results because the search engine does not understand the context of the query (e.g., “my recent invoices over $5k from last quarter”).
Goal
Deliver a context‑aware, guided search experience that: