Define notification boundary for unified inbox contributions #1

Open
opened 2026-07-09 15:05:18 +02:00 by zemion · 0 comments
Owner

Keep notifications responsible for delivery and notification-owned acknowledgement while contributing inbox items without owning task, postbox, workflow, or approval semantics.

Source concept/wiki doc: govoplan-notifications/docs/NOTIFICATION_INBOX_BOUNDARY.md.

Acceptance criteria:

  • Notification-owned inbox contribution fields are documented.
  • Delivery attempts, failures, acknowledgement, and dismissal boundaries are explicit.
  • Task/postbox/workflow/approval actions remain owned by their modules.

Context recovered from previous GovOPlaN planning chats and consolidated into the roadmap/docs on 2026-07-09.

Keep notifications responsible for delivery and notification-owned acknowledgement while contributing inbox items without owning task, postbox, workflow, or approval semantics. Source concept/wiki doc: `govoplan-notifications/docs/NOTIFICATION_INBOX_BOUNDARY.md`. Acceptance criteria: - [ ] Notification-owned inbox contribution fields are documented. - [ ] Delivery attempts, failures, acknowledgement, and dismissal boundaries are explicit. - [ ] Task/postbox/workflow/approval actions remain owned by their modules. Context recovered from previous GovOPlaN planning chats and consolidated into the roadmap/docs on 2026-07-09. <!-- govoplan-recovered-concept:8845f67a3000f3d0 -->
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: add-ideas/govoplan-notifications#1
No description provided.