[Feature] Complete the Addresses provider for AdreMa distribution lists #1

Closed
opened 2026-07-06 21:44:12 +02:00 by zemion · 4 comments
Owner

Outcome

Addresses provides address books, contact points, classical address lists, communication-governance facts, and source provenance to the AdreMa vertical. The core audience/list product is Distribution Lists #5.

The evidence-based architecture is maintained in the Distribution Lists repository: AdreMa Capability Assessment And Distribution-List Roadmap.

Delivered Addresses Foundation

  • Scoped local address books and contact CRUD.
  • Multiple email, phone, and postal contact points.
  • vCard import/export and CardDAV synchronization.
  • Static classical address lists.
  • Read-only lookup, writer decisions, provenance, and immutable email-recipient snapshots.

Remaining Addresses Work

  • Contact-point consent, suppression, preference, and communication-purpose facts: #9.
  • Deduplication, merge, quality, provenance, and audit history: #10.
  • Channel-neutral contact-point resolution and frozen postal snapshots: #14.
  • Additional address source/import portfolio decomposed into independently tracked work: #15-#21 and GovOPlaN/govoplan-connectors#9.

Boundary

  • Organizations owns units and function definitions.
  • IDM owns typed groups, identity relationships, effective function assignments, and their validity/provenance.
  • Distribution Lists owns static/dynamic operational audiences, mixed expansion, and immutable expansion evidence.
  • Addresses may preserve vCard KIND/RELATED values and stable provider links, but does not create a second party or organizational relationship authority.

Completion Criteria

This Addresses contribution closes when Distribution Lists can obtain explainable, purpose-aware contact-point candidates and immutable postal/email snapshots without importing Addresses internals. The AdreMa umbrella itself is tracked in Distribution Lists #5.

## Outcome Addresses provides address books, contact points, classical address lists, communication-governance facts, and source provenance to the AdreMa vertical. The core audience/list product is [Distribution Lists #5](https://git.add-ideas.de/GovOPlaN/govoplan-dist-lists/issues/5). The evidence-based architecture is maintained in the Distribution Lists repository: [AdreMa Capability Assessment And Distribution-List Roadmap](https://git.add-ideas.de/GovOPlaN/govoplan-dist-lists/src/branch/main/docs/ADREMA_CAPABILITY_ASSESSMENT.md). ## Delivered Addresses Foundation - [x] Scoped local address books and contact CRUD. - [x] Multiple email, phone, and postal contact points. - [x] vCard import/export and CardDAV synchronization. - [x] Static classical address lists. - [x] Read-only lookup, writer decisions, provenance, and immutable email-recipient snapshots. ## Remaining Addresses Work - [x] Contact-point consent, suppression, preference, and communication-purpose facts: #9. - [x] Deduplication, merge, quality, provenance, and audit history: #10. - [x] Channel-neutral contact-point resolution and frozen postal snapshots: #14. - [x] Additional address source/import portfolio decomposed into independently tracked work: #15-#21 and GovOPlaN/govoplan-connectors#9. ## Boundary - Organizations owns units and function definitions. - IDM owns typed groups, identity relationships, effective function assignments, and their validity/provenance. - Distribution Lists owns static/dynamic operational audiences, mixed expansion, and immutable expansion evidence. - Addresses may preserve vCard `KIND`/`RELATED` values and stable provider links, but does not create a second party or organizational relationship authority. ## Completion Criteria This Addresses contribution closes when Distribution Lists can obtain explainable, purpose-aware contact-point candidates and immutable postal/email snapshots without importing Addresses internals. The AdreMa umbrella itself is tracked in Distribution Lists #5.
zemion added this to the Module And Integration Roadmap milestone 2026-07-06 21:44:12 +02:00
Author
Owner

Codex State: note

Summary

  • Split the address roadmap into concrete implementation issues: #3, #4, #5, #6, #7, #8, #9, and #10.
  • Added architecture and implementation-plan docs in docs/ADDRESS_MODULE_ARCHITECTURE.md and docs/IMPLEMENTATION_PLAN.md.
  • This issue can stay as the broad umbrella for Adrema-style address and distribution-list management.
    '',
    2:
## Codex State: note ### Summary - Split the address roadmap into concrete implementation issues: #3, #4, #5, #6, #7, #8, #9, and #10. - Added architecture and implementation-plan docs in `docs/ADDRESS_MODULE_ARCHITECTURE.md` and `docs/IMPLEMENTATION_PLAN.md`. - This issue can stay as the broad umbrella for Adrema-style address and distribution-list management. '', 2:
Author
Owner

Codex State: progress

Summary

  • Implemented classical address-list backend support in govoplan-addresses: address-list tables, API/service layer, permissions, manifest ownership, tests, and addresses.recipient_source exposure using addresses:address_list:<id> source IDs.
  • Documented the boundary: address lists remain address-domain groupings; operational mixed Verteiler/distribution lists move to govoplan-dist-lists.
  • Created focused govoplan-dist-lists issues for DTO/contract, local implementation, and UI/provider integrations.

Remaining In Addresses

  • Address-list management UI and campaign picker polish.
  • Dynamic address-domain segments.
  • Consent, suppression, communication preferences, and privacy policy behavior.
## Codex State: progress ### Summary - Implemented classical address-list backend support in `govoplan-addresses`: address-list tables, API/service layer, permissions, manifest ownership, tests, and `addresses.recipient_source` exposure using `addresses:address_list:<id>` source IDs. - Documented the boundary: address lists remain address-domain groupings; operational mixed `Verteiler`/distribution lists move to `govoplan-dist-lists`. - Created focused `govoplan-dist-lists` issues for DTO/contract, local implementation, and UI/provider integrations. ### Remaining In Addresses - Address-list management UI and campaign picker polish. - Dynamic address-domain segments. - Consent, suppression, communication preferences, and privacy policy behavior.
zemion added
priority
p1
status
in-progress
and removed
priority
p2
status
ready
labels 2026-07-31 11:40:59 +02:00
zemion changed title from [Feature] Define Adrema-style address and distribution-list management to [Feature] Complete the Addresses provider for AdreMa distribution lists 2026-07-31 14:49:01 +02:00
zemion added the module/dist-lists label 2026-07-31 14:51:49 +02:00
Author
Owner

Progress update: #9 is complete in GovOPlaN/govoplan-addresses@41ccd4c, and Campaign consumption is complete in GovOPlaN/govoplan-campaign@82ddc0c.

This umbrella remains open for the explicitly listed work:

  • #10 deduplication/merge/quality and richer provenance history;
  • #14 channel-neutral resolution plus frozen postal snapshots;
  • #8 and Connectors #9 additional source/import profiles.

The AdreMa audience/segment authority remains Distribution Lists, not Addresses.

Progress update: #9 is complete in GovOPlaN/govoplan-addresses@41ccd4c, and Campaign consumption is complete in GovOPlaN/govoplan-campaign@82ddc0c. This umbrella remains open for the explicitly listed work: - #10 deduplication/merge/quality and richer provenance history; - #14 channel-neutral resolution plus frozen postal snapshots; - #8 and Connectors #9 additional source/import profiles. The AdreMa audience/segment authority remains Distribution Lists, not Addresses.
Author
Owner

Implemented and verified end to end.

  • Addresses quality, provenance, deduplication, reversible merge, and recovery: 19e9096 (#10).
  • Versioned channel-neutral contact-point resolution and immutable source snapshots: 2e78b9a (#14).
  • Same-transaction source revision normalization for SQLite and UTC-aware rows: e60339a.
  • Distribution Lists consumption, bounded source paging, purpose/address-purpose/fallback/locale/postal-format controls, explainable exclusions, legacy fallback, and immutable expansion evidence: GovOPlaN/govoplan-dist-lists commit 8099e34.
  • Additional connector/import formats were decomposed under #15-#21; they extend source coverage but do not block this provider contract.

Verification: 35 Addresses tests, 10 Distribution Lists tests, both Ruff suites, module TypeScript check, integrated Core WebUI production build and bundle budgets, 64/64 manifest scan, strict cross-repository contract scan, and a real Addresses -> Distribution Lists postal snapshot smoke test all pass.

The completion criterion is satisfied: Distribution Lists consumes the public addresses.contact_point_resolution contract without importing Addresses internals and freezes exact email/postal targets, contact-point IDs, revisions, fingerprints, explanations, and decision provenance.

Implemented and verified end to end. - Addresses quality, provenance, deduplication, reversible merge, and recovery: `19e9096` (#10). - Versioned channel-neutral contact-point resolution and immutable source snapshots: `2e78b9a` (#14). - Same-transaction source revision normalization for SQLite and UTC-aware rows: `e60339a`. - Distribution Lists consumption, bounded source paging, purpose/address-purpose/fallback/locale/postal-format controls, explainable exclusions, legacy fallback, and immutable expansion evidence: GovOPlaN/govoplan-dist-lists commit `8099e34`. - Additional connector/import formats were decomposed under #15-#21; they extend source coverage but do not block this provider contract. Verification: 35 Addresses tests, 10 Distribution Lists tests, both Ruff suites, module TypeScript check, integrated Core WebUI production build and bundle budgets, 64/64 manifest scan, strict cross-repository contract scan, and a real Addresses -> Distribution Lists postal snapshot smoke test all pass. The completion criterion is satisfied: Distribution Lists consumes the public `addresses.contact_point_resolution` contract without importing Addresses internals and freezes exact email/postal targets, contact-point IDs, revisions, fingerprints, explanations, and decision provenance.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-addresses#1