feat(postbox): reconcile lifecycle notifications
This commit is contained in:
@@ -108,6 +108,16 @@ an independently readable copy in the next frozen function Postbox. The
|
||||
`govoplan.postbox.dispatch_routes` periodic Core worker drains due routes when
|
||||
Celery beat and a worker consuming the `postbox` queue are enabled.
|
||||
|
||||
That worker also reconciles current IDM incumbencies in batches against a
|
||||
durable metadata-only cursor. Assignment, delegation, vacancy, and
|
||||
reassignment changes emit versioned platform events and optional in-app
|
||||
Notifications for newly eligible current holders. Delivery, action-required,
|
||||
escalation-due, read, and acknowledgement events link back to Postbox-owned
|
||||
resources without copying message subjects, bodies, or attachment details into
|
||||
lifecycle events. Notification preferences, quiet periods, and future external
|
||||
channel policy remain owned by Notifications; every deep link rechecks current
|
||||
Postbox access.
|
||||
|
||||
Postboxes expose three configurable content-protection profiles. The recommended
|
||||
`server_envelope_v1` profile stores message bodies as ciphertext through an
|
||||
institution-controlled Encryption vault and fails closed if its capability or
|
||||
|
||||
Reference in New Issue
Block a user