THE FIELD GUIDE / OPERATIONS
Live notifications & attention alerts
A persistent bell, asynchronous updates and a durable per-user review center.
Know when a human is needed
The notification bell stays available throughout the authenticated workspace on desktop, tablet and mobile. Its unread count and severity cue lead to a compact recent panel and a paginated notification center. Filter by unread/all, severity, server and event type, then follow an exact link to the result, incident, operation, health problem or pending review.
Receive updates while you work
Authenticated same-origin server-sent events signal committed changes. The client fetches permission-filtered data without interrupting dialogs or stealing focus. Stream frames carry neither notification text nor raw evidence. Significant triage findings, failed or blocked work, response/recovery holds, meaningful health or coverage failures and AI configuration/budget blockers remain discoverable after a toast disappears. Routine successes and unchanged known-good cache hits do not flood the feed.
Reconnect and catch up
The live feed uses event identity, heartbeat and cursor replay, with authoritative paginated catch-up after reload, sleep, offline periods or reconnection. Pruned history or invalid cursors cause an explicit resynchronization rather than a false complete-history claim. Connection state and last synchronization stay visible; a polling fallback reports degraded delivery.
Read state belongs to you
Read, unread and dismiss state persists for each user across sessions and tabs. Reading or dismissing a notification does not globally acknowledge or resolve its incident, approve AI output or run a response. Reopened, changed or escalated findings resurface as appropriate. Missing or retained-only linked records are explained.
Keep access and delivery separate
Current role and subject permissions filter counts, payloads and detail reads. Sessions and permissions are rechecked, account switching resets personal state, and untrusted event text is escaped. Notifications work without browser/OS notification permission, SMTP or webhooks, and deterministic attention events continue with AI disabled or paused.
Use external delivery alongside the bell
Account → Operations configures verified-TLS SMTP or HTTPS webhook delivery. A durable outbox retries with backoff; stable event IDs support receiver deduplication. Acknowledgement and escalation follow the existing role-checked workflows. The in-app center preserves those external channel settings and alert-lifecycle boundaries.
Open the application reference for capability scope and technical details.
Open Open SECURITY_IMPLEMENTATION.md on GitHub ↗