[Task] Which event transport is the first production target: DB outbox only, Redis/Celery, or pluggable dispatch? #184

New Issue

zemion · 2026-07-06T15:22:42+02:00

zemion commented

2026-07-06 15:22:42 +02:00

Imported from a backlog-like text file.

Source: /mnt/DATA/Nextcloud/ADD ideas UG/Products/govoplan/split-concept-action-plan.md
Line: 433
Source kind: product
Section: GovOPlaN Split Concept and Action Plan > Key Decisions Needed

Imported item:

Which event transport is the first production target: DB outbox only, Redis/Celery, or pluggable dispatch?

Imported from a backlog-like text file. - Source: `/mnt/DATA/Nextcloud/ADD ideas UG/Products/govoplan/split-concept-action-plan.md` - Line: `433` - Source kind: `product` - Section: `GovOPlaN Split Concept and Action Plan > Key Decisions Needed` Imported item: ```text Which event transport is the first production target: DB outbox only, Redis/Celery, or pluggable dispatch? ```

zemion added this to the Split Concept Action Plan milestone 2026-07-06 15:22:42 +02:00

zemion added the

source/backlog-import

codex/ready

labels 2026-07-07 23:10:57 +02:00

zemion added the

status

triage

label 2026-07-08 02:24:58 +02:00

zemion commented

2026-07-08 20:59:12 +02:00

Codex State: done

Summary

Event transport decision documented: first production target is the database outbox with in-process immediate dispatch; Redis/Celery remains worker infrastructure, not the authoritative event transport.

Changed Files

docs/EVENTS_AND_AUDIT.md

Verification

Focused checks passed where available; see working-tree validation summary in Codex final response.

## Codex State: done ### Summary - Event transport decision documented: first production target is the database outbox with in-process immediate dispatch; Redis/Celery remains worker infrastructure, not the authoritative event transport. ### Changed Files - `docs/EVENTS_AND_AUDIT.md` ### Verification - Focused checks passed where available; see working-tree validation summary in Codex final response.

zemion closed this issue

2026-07-08 20:59:27 +02:00

Sign in to join this conversation.