Define unified inbox aggregation contract #1

New Issue

2026-07-09T15:05:13+02:00

zemion commented

2026-07-09 15:05:13 +02:00

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.

zemion added the area/api codex/ready module/tasks

labels 2026-07-29 14:15:11 +02:00

zemion commented

2026-08-06 14:12:12 +02:00

The unified inbox contract is now the immediate human-work spine for the service-to-decision reference journey. Implementation will aggregate module-owned attention items while Tasks owns explicit work items; Workflow Engine remains the process owner and Notifications remains an attention channel.

The unified inbox contract is now the immediate human-work spine for the service-to-decision reference journey. Implementation will aggregate module-owned attention items while Tasks owns explicit work items; Workflow Engine remains the process owner and Notifications remains an attention channel.

zemion commented

2026-08-06 16:17:36 +02:00

Codex State: done

Implemented and pushed in govoplan-core@d65d7a8 and govoplan-tasks@3cdab59.

Core now owns a versioned work-item/provider contract carrying the owner module, tenant-safe visibility through typed assignments and current provider authorization, summary, priority, due date, required action, deep link, source revisions, and provenance.
Providers are registered through the Core registry; optional modules do not import Tasks or each other.
Source modules retain command and completion authority. Tasks only aggregates their current projections.
Contract validation, provider isolation, tenant/module filtering, and module-permutation tests are included.

Verification: Core work-contract tests, Tasks backend/migration tests, manifest checks, focused product checks, and Tasks-only/contributor/full-product WebUI builds passed.

## Codex State: done Implemented and pushed in `govoplan-core@d65d7a8` and `govoplan-tasks@3cdab59`. - Core now owns a versioned work-item/provider contract carrying the owner module, tenant-safe visibility through typed assignments and current provider authorization, summary, priority, due date, required action, deep link, source revisions, and provenance. - Providers are registered through the Core registry; optional modules do not import Tasks or each other. - Source modules retain command and completion authority. Tasks only aggregates their current projections. - Contract validation, provider isolation, tenant/module filtering, and module-permutation tests are included. Verification: Core work-contract tests, Tasks backend/migration tests, manifest checks, focused product checks, and Tasks-only/contributor/full-product WebUI builds passed.

zemion closed this issue

2026-08-06 16:17:37 +02:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-tasks#1