[Feature] Emit Postbox delivery, vacancy, assignment, and escalation notifications #20

Open
opened 2026-07-28 18:59:05 +02:00 by zemion · 1 comment
Owner

Outcome

Eligible incumbents receive useful notifications for durable Postbox events without duplicating the Postbox as another notification store or leaking message content.

Acceptance criteria

  • Emit versioned events for delivery accepted, newly visible through assignment/delegation, vacancy, escalation due, reassignment, read/acknowledged, and action required.
  • Notifications resolves current recipients from IDM in batches and links back to the source postbox/message and acting context.
  • Do not include sensitive body/attachment content in event payloads; include only stable ids, classification-safe summary, and provenance.
  • Deduplicate retries and assignment churn; withdrawing access removes future deep-link usability but does not rewrite audit history.
  • Respect user notification preferences, quiet periods, classification restrictions, and future email/push channel policy.
  • Keep notification delivery optional: Postbox remains correct when Notifications is absent.

Dependencies

Builds on effective IDM lifecycle events, Postbox delivery/access foundations, and parent user story #16.

## Outcome Eligible incumbents receive useful notifications for durable Postbox events without duplicating the Postbox as another notification store or leaking message content. ## Acceptance criteria - Emit versioned events for delivery accepted, newly visible through assignment/delegation, vacancy, escalation due, reassignment, read/acknowledged, and action required. - Notifications resolves current recipients from IDM in batches and links back to the source postbox/message and acting context. - Do not include sensitive body/attachment content in event payloads; include only stable ids, classification-safe summary, and provenance. - Deduplicate retries and assignment churn; withdrawing access removes future deep-link usability but does not rewrite audit history. - Respect user notification preferences, quiet periods, classification restrictions, and future email/push channel policy. - Keep notification delivery optional: Postbox remains correct when Notifications is absent. ## Dependencies Builds on effective IDM lifecycle events, Postbox delivery/access foundations, and parent user story #16.
Author
Owner

Codex State: progress

Postbox emits versioned delivery/read/ack/evidence/lifecycle events and optionally dispatches one privacy-minimal in-app notification per current incumbent with a message deep link. Retries do not duplicate notifications. Newly-visible, vacancy, scheduled expiry, escalation, and preference-aware multi-channel notification behavior remain open.

## Codex State: progress Postbox emits versioned delivery/read/ack/evidence/lifecycle events and optionally dispatches one privacy-minimal in-app notification per current incumbent with a message deep link. Retries do not duplicate notifications. Newly-visible, vacancy, scheduled expiry, escalation, and preference-aware multi-channel notification behavior remain open.
zemion added
status
in-progress
and removed
status
ready
labels 2026-07-29 00:20:19 +02:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-postbox#20
No description provided.