[Epic] Deliver governed AdreMa audience selection and hybrid distribution #5

New Issue

2026-07-31T14:48:10+02:00

zemion commented

2026-07-31 14:48:10 +02:00

Outcome

Distribution Lists is the core GovOPlaN target for AdreMa-style audience selection and reusable operational Verteiler.

The evidence-based architecture is documented in AdreMa Capability Assessment And Distribution-List Roadmap.

Module Composition

Addresses: contact points, postal purposes, preference/consent/suppression facts.
Organizations/IDM: units, functions, typed groups, identities, and effective-dated relationships.
Datasources/Connectors/Dataflow: governed source states and complex audience evaluation.
Distribution Lists: versioned definitions, expansion, explanation, and immutable snapshots.
Templates/Campaign/Files: printable or digital output, hybrid routing, and artifacts.
Audit/Policy/Reporting/Workflow: evidence, eligibility decisions, analysis, and guided execution.

Work Packages

#1 provider-neutral DTO and expansion contract.
#2 local persistent lists and raw/address entries.
#3 provider integrations and operator UI.
#4 Campaign recipient-source and immutable snapshot integration.
#6 parameterized dynamic audiences backed by governed Dataflow revisions.
#7 governed channel preference/opt-in resolution.
GovOPlaN/govoplan-idm#7 typed groups and effective-dated relationships.
GovOPlaN/govoplan-dataflow#18 synthetic AdreMa golden flow.
GovOPlaN/govoplan-templates#4 typed printable output.
GovOPlaN/govoplan-campaign#90 hybrid Campaign review/output.

Completion Criteria

A user can define or reuse a permissioned audience, preview and explain its membership, freeze exact recipients and channel decisions, produce reviewed printable or digital output, and prove source, rule, policy, template, actor, artifact, and outcome provenance. Every provider and consumer integration degrades cleanly when absent.

No separate Print module is part of this architecture. Templates owns printable output; a managed printer endpoint, if needed later, is a connector-backed artifact export destination.

## Outcome Distribution Lists is the core GovOPlaN target for AdreMa-style audience selection and reusable operational `Verteiler`. The evidence-based architecture is documented in [AdreMa Capability Assessment And Distribution-List Roadmap](https://git.add-ideas.de/GovOPlaN/govoplan-dist-lists/src/branch/main/docs/ADREMA_CAPABILITY_ASSESSMENT.md). ## Module Composition - Addresses: contact points, postal purposes, preference/consent/suppression facts. - Organizations/IDM: units, functions, typed groups, identities, and effective-dated relationships. - Datasources/Connectors/Dataflow: governed source states and complex audience evaluation. - Distribution Lists: versioned definitions, expansion, explanation, and immutable snapshots. - Templates/Campaign/Files: printable or digital output, hybrid routing, and artifacts. - Audit/Policy/Reporting/Workflow: evidence, eligibility decisions, analysis, and guided execution. ## Work Packages - [ ] #1 provider-neutral DTO and expansion contract. - [ ] #2 local persistent lists and raw/address entries. - [ ] #3 provider integrations and operator UI. - [ ] #4 Campaign recipient-source and immutable snapshot integration. - [ ] #6 parameterized dynamic audiences backed by governed Dataflow revisions. - [ ] #7 governed channel preference/opt-in resolution. - [ ] GovOPlaN/govoplan-idm#7 typed groups and effective-dated relationships. - [ ] GovOPlaN/govoplan-dataflow#18 synthetic AdreMa golden flow. - [ ] GovOPlaN/govoplan-templates#4 typed printable output. - [ ] GovOPlaN/govoplan-campaign#90 hybrid Campaign review/output. ## Completion Criteria A user can define or reuse a permissioned audience, preview and explain its membership, freeze exact recipients and channel decisions, produce reviewed printable or digital output, and prove source, rule, policy, template, actor, artifact, and outcome provenance. Every provider and consumer integration degrades cleanly when absent. No separate Print module is part of this architecture. Templates owns printable output; a managed printer endpoint, if needed later, is a connector-backed artifact export destination.