PH6.2 — Notifications: delivery, read state, in-app bell #43

Open
opened 2026-09-11 09:02:18 +00:00 by bart · 0 comments
Collaborator

Parent

Row PH6.2 in docs/12-implementation-plan.md (branch, owned paths and doc section are defined there).

What to build

Notification rows produced by runs, events and publishes reach the user in an in-app bell with unread count and mark-as-read; kinds render from codes + payload.

Acceptance criteria

  • Notification endpoints list, mark read; read state is per user
  • Bell shows unread count and updates without reload
  • Every notification kind has nl/en templates (parity check covers kinds)

Blocked by

  • #20 — Plan orchestration: snapshot builder, result writer, solver_run/plan_version lifecycle, publish/supersede
  • #13 — Web shared UI: Optimus wrappers, pipes, view-model types, generic admin CRUD, store slice pattern
## Parent Row **PH6.2** in `docs/12-implementation-plan.md` (branch, owned paths and doc section are defined there). ## What to build Notification rows produced by runs, events and publishes reach the user in an in-app bell with unread count and mark-as-read; kinds render from codes + payload. ## Acceptance criteria - [ ] Notification endpoints list, mark read; read state is per user - [ ] Bell shows unread count and updates without reload - [ ] Every notification kind has `nl`/`en` templates (parity check covers kinds) ## Blocked by - #20 — Plan orchestration: snapshot builder, result writer, solver_run/plan_version lifecycle, publish/supersede - #13 — Web shared UI: Optimus wrappers, pipes, view-model types, generic admin CRUD, store slice pattern
Sign in to join this conversation.
No labels
ready-for-agent
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
patrick/Polaris#43
No description provided.