Define unified inbox aggregation contract #1

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

Define a unified inbox contribution contract for tasks, workflow exceptions, postbox messages, notifications, approvals, and other attention items while preserving module ownership.

Source concept/wiki doc: govoplan-tasks/docs/UNIFIED_INBOX_CONCEPT.md.

Acceptance criteria:

  • Inbox item DTOs include owning module, visibility, summary, priority, due date, required action, source references, and provenance links.
  • Domain modules remain owners of item commands and completion semantics.
  • The aggregation surface uses core-mediated capabilities rather than module-to-module imports.

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

Define a unified inbox contribution contract for tasks, workflow exceptions, postbox messages, notifications, approvals, and other attention items while preserving module ownership. Source concept/wiki doc: `govoplan-tasks/docs/UNIFIED_INBOX_CONCEPT.md`. Acceptance criteria: - [ ] Inbox item DTOs include owning module, visibility, summary, priority, due date, required action, source references, and provenance links. - [ ] Domain modules remain owners of item commands and completion semantics. - [ ] The aggregation surface uses core-mediated capabilities rather than module-to-module imports. Context recovered from previous GovOPlaN planning chats and consolidated into the roadmap/docs on 2026-07-09. <!-- govoplan-recovered-concept:ff851b920d7ca464 -->
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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