docs: narrow AdreMa ownership to address provider

docs/ADDRESS_MODULE_ARCHITECTURE.md

@@ -17,7 +17,7 @@ targets layered on top of the same local model and sync contracts.
 `govoplan-addresses` owns:
 
 - scoped address books
-- contacts, organizations, households, and postal/email/phone address data
+- vCard-compatible contacts and postal/email/phone contact-point data
 - vCard import/export and vCard-compatible field mapping
 - reusable recipient sources and classical address lists
 - contact tags, categories, communication preferences, consent, and legal basis
@@ -31,9 +31,12 @@ It does not own:
 - mail transport, mailbox access, or delivery queues
 - calendar events or iCalendar event storage
 - global identity authentication or authorization decisions
-- organization structure or internal function assignments
-- operational distribution lists/`Verteiler` with mixed users, identities,
-  groups, functions, roles, raw recipients, and nested lists
+- IDM identities, typed groups, effective-dated relationships, or identity
+  lifecycle state
+- organization structures, units, function definitions, or function
+  assignments
+- operational distribution lists/`Verteiler` with mixed address contacts, IDM
+  identities/groups, functions, raw targets, Dataflow rows, and nested lists
 
 ## Scopes
 
@@ -55,7 +58,8 @@ fields:
 - name components and formatted names
 - nicknames and display names
 - email addresses, phone numbers, postal addresses, URLs, notes, categories
-- organizations, titles, roles, departments, and relationships
+- organization, title, role, department, `KIND`, and `RELATED` values needed for
+  vCard round-trip compatibility
 - birthday/anniversary where allowed by policy
 - photos/avatars where storage and privacy policy allow them
 - calendar or scheduling addresses where present
@@ -180,12 +184,20 @@ stable IDs while keeping their own domain evidence. Cross-module UI must hide
 write actions when no writable target exists, or show the writer decision
 message when a disabled action remains visible for context.
 
-Operational distribution lists belong in `govoplan-dist-lists`. They may later
-consume address lists as one entry type, but they own mixed recipient expansion
-for users, identities, organization units, groups, functions, roles, raw
-recipients, and nested lists. Workflow and Tasks own `Umlauf` execution state;
+Operational distribution lists and reusable dynamic segments belong in
+`govoplan-dist-lists`. They may consume address lists as one entry type, but
+they own mixed recipient expansion for address contacts, IDM identities and
+typed groups, organization units, functions/effective incumbents, raw targets,
+Dataflow-backed rows, and nested lists. Workflow owns `Umlauf` execution state;
 distribution lists define who is included, not how work circulates.
 
+Organizations owns unit and function definitions. IDM owns effective-dated
+identity-to-function assignments and typed group relationships. Identity
+lifecycle status is not a business audience status; a selectable business
+status is represented by a group, function, or effective-dated relationship.
+Addresses may link contact points to stable provider references without copying
+those provider-owned facts.
+
 ## Deferred Work
 
 The following are valuable but not required for the first functional milestone:
@@ -193,6 +205,6 @@ The following are valuable but not required for the first functional milestone:
 - automatic deduplication and merge suggestions
 - two-way sync conflict UI
 - Microsoft/Google connectors
-- household and relationship editing
+- richer vCard `KIND`/`RELATED` round-trip and provider-reference linking
 - advanced consent-policy automation
 - contact activity timeline across all modules