BryanNetCustomer notification event taxonomy
Prerequisites and authority
Use this reference with your installed release. Internal implementation routes and settings are not public integration contracts.
Customer event and notification taxonomy
Business events, stored notifications and external deliveries are separate records. A delivery failure does not reverse the event. In-app history is available while using the application; OS/browser push with the app closed is outside scope.
| Event family | Intended examples | Verification requirement |
|---|---|---|
| Subscription | Activated, expiring, expired, queued transition | Actual emitted events and timing |
| Internet connection | Login, logout, concurrency/admin disconnect | Router event authenticity and accounting |
| Device/account | Registered, removed, blocked or account changes | Actual supported events and recipients |
| Service | Maintenance/restoration notices | Supported automation versus manual notice |
The table groups notification purposes; it does not mean every event is delivered through every channel. Check the stored notification, enabled delivery channel and operation history separately when diagnosing a missing message.
Telegram is an external customer channel; in-app storage/history is separate. SMTP/email availability requires its own release check. Administrator notifications are not automatically customer broadcasts.
No customer category opt-out controls are required. Record unread/read behavior separately from delivery acknowledgement. Repeated event retries must not produce misleading duplicate notices.
For each supported event, finalize canonical identifier, trigger, audience, channel, stored payload, action link, retries, deduplication and entitlement constraints. Keep credentials/PII out of examples. Customer notifications and self-service account settings and Notifications or email not delivered cover customer use and diagnosis.
Related guides
Related guides: Configuration reference (env vars, ports, URLs), Docker services, Compose files and persistent volumes, Database diagnostics and safe query reference, Subscription and provisioning state model.